EDItEUR's OA in ONIX Presentation, NISO eBook Bibliographic Metadata Recommended Practice

[Christina Drummond]

Greetings All:

First of all, thank you for signing up to participate in this OAeBU Data Trust Technical Standards and Norms working group, where we'll be discussing the pros, cons, and intricacies of the norms and standards impacting the data trust's infrastructure.

To get us started, I wanted to make everyone aware of a few resources that have crossed my desk this week: 

• Graham Bell at EDItEUR's Open Access products in ONIX presentation, which addresses topics such as unique issues when handling OA metadata within ONIX (3:58 mark) and challenges of applying ONIX specifically to OA monographs (14:29 mark)
• the United States' National Information Standards Organization's E-Book Bibliographic Metadata Requirements in the Sale, Publication, Discovery, and Preservation Supply Chain (E-Book Metadata) Working Group just opened a comment period on draft Recommended Practice pertaining to "minimal metadata requirements necessary to describe e-books in order to support sales, discovery, delivery, deaccessioning, and preservation, and identify the most effective and efficient way for metadata to be moved through the entire supply chain." 
• If you have thoughts for the data trust based on either the draft Recommended Practice document, or the comments that have been submitted, let's hear them. 
• As a global effort with a focus on usage data, if this group feels there is a specific need to comment to NISO given the expected needs of the data trust, we have an open opportunity through August 2nd. 

Please feel free to share other resources that pertain to the technical design of the OA monograph usage data trust as you encounter them. 

Discussion topics will be forthcoming from our technical team. In the meantime, feel free to say hello, respond and/or introduce yourself or any resources that you're working with these days. 

Have a great weekend,

Christina

PS: To introduce myself, in addition to being the Program Officer for the OA eBook Usage (OAeBU) Data Trust effort, I'm a longtime data policy geek driven by impact and a deep love for the role of data visualizations in data-driven decision-making. After starting my career query and BI dashboard building to support B2B and nonprofit operations, I shifted into data policy, research development and program management in nonprofits and academia. I focused on data analysis heavily in my social science training, prior to earning my MA in International Science and Technology Policy. I hold certifications in international business, design thinking, and information privacy. Aussi, je parle Francaise meilleur de j'écrit.

[Ronald Snijder]

Dear Christina,

 

In 2016, Jisc and OAPEN created a minimum set of OA books metadata:

 

Jisc and OAPEN: Metadata for open access monographs (2016)

The guide ‘Metadata for open access monographs’ presents a metadata model for OA monographs. The model was created as part of the project ‘Investigating OA monograph services’, conducted by Jisc and OAPEN. 

Download: Jisc and OAPEN: Metadata for open access monographs (2016)

See also: https://oapen.org/resources/1427011-oa-monograph-publisher-guides

 

Kind regards,

Ronald Snijder, PhD

 

OAPEN Foundation

Prins Willem-Alexanderhof 5

PO Box 90407

2509 LK The Hague

The Netherlands

 

email: r.sn...@oapen.org

www.oapen.org

 

ORCID: 0000-0001-9260-4941

--
This message was generated through one of the OA eBook Usage Data Trust community forums. Learn more about this Andrew W. Mellon supported 2020-2022 pilot project at https://educopia.org/data_trust/.
---
To post to this group, email OAeBU-DataTrust-N...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "OA eBU Data Trust Technical Norms/Standards Working Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to OAeBU-DataTrust-Norms-S...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/OAeBU-DataTrust-Norms-Standards-WG/7d7539a6-6801-434f-ae3f-2d41860d8a68o%40googlegroups.com.

[Charles Watkinson]

Dear Ronald,

I hadn't seen the Jisc resource before -- thank you for sharing. Can you explain how this maps to MARC and ONIX standards? Surely those are the metadata standards OA ebook publishers should focus on, rather than developing a third and separate system. I know that ONIX and MARC are sometimes thought to be too complicated for smaller publishers to manage, but COPIM is working on making that easier and there are already plenty of libraries and vendors available to help.

By 2016, EDitEUR has already documented a standard for "Open Access Monographs in ONIX for Books"

It took until 2018 for the German National Library and OCLC to introduce requirements for Open Access for MARC. 

All to say, I hope that the Data Trust will continue to work to advance current standards already used within the book supply chain rather than being tempted to define another.

Charles

To view this discussion on the web visit https://groups.google.com/d/msgid/OAeBU-DataTrust-Norms-Standards-WG/EA9E784EABE7454EADDB409DD6E26093904DD622%40MBX-SRV-P200.wpakb.kb.nl.

--

Charles Watkinson

Director, University of Michigan Press

Associate University Librarian, Publishing

University of Michigan Library

839 Greene Street, Ann Arbor, MI 48104-3209

(office) 734 936 0452, (mobile) 609 933 2410

wat...@umich.edu

https://orcid.org/0000-0002-9453-6695

My pronouns are he / him / his

Learn more about how Michigan Publishing is making an impact and advancing the mission of our parent institution at https://www.publishing.umich.edu/ 

[eric]

Hi everyone! 

Relevant to ebook usage data, reading in mobile apps in our ecosystem is increasingly being driven by OPDS syndication, which defines a number of data elements ignored by MARC, and handled sort-of in ONIX. Mobile apps need acquisition/access URLs and metadata, and cover images. If a "Data Trust" ignores mobile apps, it will miss all the usage associated with these apps.

https://specs.opds.io/opds-1.2

Currently, the usage of free ebooks lacking ISBNs is larger than usage of free ebooks with proper ISBNs assigned. I'm currently assisting Project Gutenberg with their ebook generation and distribution. PG currently delivers about 5 million ebooks per month; none of them have ISBNs. Similarly, a majority of "free programming books" (https://ebookfoundation.github.io/free-programming-books/) do not have ISBNs assigned. At the work level, many free -licensed ebooks have hundreds of ISBNs associated with then; as creation of alternate versions a derivative works is both allowed and encouraged. A robust facility for usage data will need to go beyond ISBN for identification, if for no other reason than that real systems don't have a good grasp on the differently flavored ISBNs in circulation.

It's increasingly important to capture the lineage of derivative ebook versions, especially in the area of open textbooks. But that's probably beyond the scope of OAeBU.

Eric Hellman
President, Free Ebook Foundation
Founder, Unglue.it https://unglue.it/
https://go-to-hellman.blogspot.com/
twitter: @gluejar

[Ronald Snijder]

Dear Charles,

 

The Jisc/OAPEN document is more at the abstraction level of FRBR (https://www.oclc.org/research/activities/frbr.html#background) than ONIX or MARC. It describes the main objects 1. Book; 2. Creator; 3. Format; 4. Collection and what should be known about them.

 

In fact, both ONIX and MARC enable all the required metadata.

 

Hope this explains it a bit better!

 

Kind regards,

Ronald Snijder, PhD

 

OAPEN Foundation

Prins Willem-Alexanderhof 5

PO Box 90407

2509 LK The Hague

The Netherlands

 

email: r.sn...@oapen.org

www.oapen.org

 

ORCID: 0000-0001-9260-4941

 

To view this discussion on the web visit https://groups.google.com/d/msgid/OAeBU-DataTrust-Norms-Standards-WG/CA%2BUve54z0jBP2qjpcOtKxSqpULv7nwU7z3gyHrz-yJh8tvzUPQ%40mail.gmail.com.