1 / 33

CrossRef Deposit Schema 2.0

CrossRef Deposit Schema 2.0. Bruce D. Rosenblum I NERA I NCORPORATED Innovative Software Solutions CrossRef Annual Meeting September 26, 2002. Presentation Overview. What's new in 2.0 Hierarchy overview Specific Issues. What's New in 2.0. It’s more than journal articles Books

yehuda
Download Presentation

CrossRef Deposit Schema 2.0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CrossRef Deposit Schema 2.0 Bruce D. Rosenblum INERA INCORPORATED Innovative Software Solutions CrossRef Annual Meeting September 26, 2002

  2. Presentation Overview • What's new in 2.0 • Hierarchy overview • Specific Issues

  3. What's New in 2.0 • It’s more than journal articles • Books • Major reference works • Conference proceedings

  4. DOI Assignment (version 0.3) • Journal • Article

  5. DOI Assignment (version 2.0) • Journal • Article • Issue • Volume • Title • Book • Volume and/or Series • Content Item (e.g. chapters, sections, etc.) • Conference • Proceedings • Paper

  6. Schema Design • Designed for linking • Based on: • Extensive review of actual citations • Publisher input • Only essential fields are required • Deposit Header • Container metadata (journal name, book title, etc.) • Publication date • DOI, URI

  7. Schema vs. DTD • W3C XML Schema • Data validation • Parsers • Conformant • Xerces 2.0 • Semi-conformant • XML Spy • Turbo XML (XML Authority) 2.2.1.100 or later

  8. 0.3 vs. 2.0 Comparison • More Hierarchy • Less redundant data • Naming Conventions • Preserved 0.3 DTD names where appropriate • Used ONIX names for some new elements • See documentation for mapping tables

  9. Header View

  10. Journal Metadata

  11. Journal Article

  12. Book Metadata

  13. Book Content Item

  14. Conference View

  15. Conference Event Metadata

  16. Conference Proceedings Metadata

  17. Conference Metadata Official Conference name including number and subject <event_metadata> <conference_name>29th International Conference on Computer Graphics and Interactive Techniques</conference_name> <conference_theme>Interactive Techniques</conference_theme> <conference_acronym>SIGGRAPH 2002</conference_acronym> <conference_number>2</conference_number> <conference_date start_year=”2002">2002</conference_date> </event_metadata> <proceedings_metadata language="en"> <proceedings_title>Proceedings of the twenty-ninth International Conference on Computer Graphics and Interactive Techniques - SIGGRAPH 2002</proceedings_title> <proceedings_subject> Computer Graphics</proceedings_subject> Annual conference slogan Popular or jargon name Proceedings cover page title Subject matter of printed proceedings

  18. Data Submission Issues • Special Characters • Unicode • Combining characters • Non-Breaking space (&#x00A0) • Face Markup • <b>, <i>, <sup>, <sub>, etc. • Math Markup • Good faith representation with Unicode and face markup

  19. General Element Comments • <publisher_item> • <publication_date> • <timestamp> • <person_name> • <collection>

  20. <publisher_item> • <identifier> • Public standard identifier • PII, SICI, DOI • <item_number> • Publisher internal identifier • Not based on public standard • item_number_type attribute • e.g. article_number in electronic-only publications

  21. <publication_date> • Assignable to item or item container • Journal: issue or article • Book: book or content item • Proceedings: proceedings or paper • Required if underlined • Allows unique online and print dates

  22. <timestamp> • Integer version number • Formatted as date/time • <head> timestamp used if not in <doi_data>

  23. <person_name> • New <suffix> element • Do not include titles, e.g. "Dr.", "Prof." • Ambiguous names: <surname> only • <surname>Leonardo da Vinci</surname> • <surname>Prince Charles</surname> • Organizations: Use <organization>, not <surname>

  24. <collection> • Designed for multiple resolution • Infinitely recursive • For future use

  25. Content-Specific Elements • Books • <content_item> • <edition_number> • Conference Proceedings • Conference metadata • <conference_name> • <conference_number> • <conference_date>

  26. Sample Book TOC

  27. <content_item> • Attributes • component_type: chapter, section, part, track, reference_entry, other • level_sequence_number • Indicates level of nesting • Reflects TOC layout • Flat schema model implies submission order if important

  28. <edition_number> • Edition number of book • Update when entire book updated • Unresolved issue: • For online content with discrete updates, when do you update the edition number • Possible solutions: • Register new DOI if chapter is significantly changed • Keep original DOI and make old versions accessible

  29. Conference Metadata Issues(1)

  30. Conference Metadata Issues (2)

  31. <conference_date> • CDATA format <conference_date>Jan. 15-17, 1997</conference> • Attribute format <conference_date start_day="15" start_month="01" start_year="1997" end_day="17” end_month="01" end_year="1997”/> • CDATA and attribute <conference_date start_day="15" start_month="01" start_year="1997" end_day="17” end_month="01" end_year="1997”> Jan. 15-17, 1997</conference>

  32. Resources • CrossRef Schema Documentation 2.0.5.pdf • and sample XML files • http://mddb2.crossref.org/doc/TechDoc.html • tech-support@crossref.org

  33. Questions? Bruce D. Rosenblum INERA INCORPORATED +1 (617) 969 - 3053 brosenblum@inera.com www.inera.com

More Related