thoth-pub / thoth Goto Github PK

Recommendation 1. COPIM must develop two metadata requirements for OA monographs, a minimum set of metadata requirements and an enriched set. Any technical report used to build the ODS needs to include both.

--database-url

Recommendation 10. COPIM to develop channels to address distributors and library systems vendors

Recommendation 11. COPIM to discuss outputs of the OAPEN workshops in order to develop this area

Instead of separate files

Recommendation 4. Further work is required to find out how researchers discover OA content.

Recommendation 12. Liaise further with LYRASIS to better understand the approach of Library Simplified and SimplyE

what happens when I do this

Recommendation 15. To conduct a number of interviews with key library discovery vendors to better understand their use of metadata in relation to that agreed by COPIM

Recommendation 16. Consider re-running the research of Wiersma & Tovstiadi for a selection of OA books once the ODS is released.

To reduce image size

Convert from db errors to http etc.

Redirect "/" to "/graphiql"

Recommendation 7. Release a briefing paper aimed at library suppliers to increase engagement

Recommendation 36. As the main supplier of data to the British Library CIP programme and to UK academic libraries, COPIM should liaise with BDS in order to understand workflows and business models

Book chapters are to be stored as work of the work_type book-chapter, and linked to the parent work through the new (M-M) work_relation table.

Changes to the data model

work_relation table

This table allows a M-M relationship of work with itself. Its attributes are: relator_work_id (FK, UUID), related_work_id (FK, UUID) and relation_type (relation_type ENUM).

For each relation we create we will need to insert two rows in this table, one for the active and one for the passive relation.

e.g., Book --- hasChild ---> Chapter and Chapter --- isChildOf ---> Book

work table

The following existing attributes must be constrained to work_type != book_chapter: edition, width, height, toc, lccn and oclc.

A new attribute page_interval needs to be added. This attribute will be constrained to work_type == book_chapter. Similar to full_title, it should be the combination of first_page and last_page (accepting both arabic and roman numerals).

Changes to the GraphQL API

• New Work attribute relations(relationType: RelationType), which returns the relation type and the related work (querying all work_relation in which the work_id matches the relator_work_id)
• Note which Work attributes are restricted to what workType
• New root query books() which returns [Work] of workType: 'monograph', 'edited-book', 'textbook', and 'journal-issue'.
• New root query chapters() which returns [Work] of workType: 'book-chapter'
• New root query bookCount()
• New root query chapterCount()
• New root query bookByDoi()
• New root query chapterByDoi()

Changes to the Export API

• Review which specifications support chapter-level data
• Restrict publisher-level outputs, except CSV, to books. discussion needed

Changes to the APP

• New relation form component to add work relations by searching an existing work and selecting the relation type in a modal
• Conditional display of constrained fields based on work_type
• Two new widgets to dashboard to display the book and chapter counts
• Two submenu items under Works: Books (/admin/books) and Chapters (/admin/chapters)

Recommendation 5. COPIM to liaise with the British Library regarding its metadata services and the Cataloguing-in-Publication (CIP) Programme

Recommendation 2. COPIM WP5 needs to develop a set of formal links with OPERAS and NBK/Library Hub in order for a two-way exchange of information and metadata. This needs to include key deliverables.

Using https://github.com/davidpdrsn/juniper-from-schema

e.g. by work_id

Recommendation 3. COPIM keeps a watching brief on this project and makes its findings available to Metadata 2020.

Recommendation 13. Some OA publishers see JSTOR as an essential part of their dissemination. Therefore, COPIM needs to engage with JSTOR

Recommendation 1. COPIM must develop two metadata requirements for OA monographs, a minimum set of metadata requirements and an enriched set. Any technical report used to build the ODS needs to include both.

Recommendation 2. COPIM WP5 needs to develop a set of formal links with OPERAS and NBK/Library Hub in order for a two-way exchange of information and metadata. This needs to include key deliverables.

Recommendation 6. COPIM to make contact with the Library of Congress committee to initiate a discussion about OA books

With an open license for metadata reuse