SHERPA/RoMEO Forthcoming Developments and the API Peter Millington Centre for Research Communications University of Nottingham RoMEO API Workshop, Repository Fringe 2010

Outline Recap of Issues & Opportunities Journal Level Data – Problems & RoMEO plans – Prototype RoMEO journal database – Implications for the API Publisher Data – Problems & RoMEO plans – Idea for revising RoMEO Colours – Implications for the API Data migration

Recap of Issues & Opportunities Things raised in this morning’s talks Things raised in the API User Survey – Need for journal-level data – Trustworthiness Authority of policy statements Historical changes – More data (esp. non-English sources), and more fields Current Major RoMEO Developments – Journal-level rights – Redesigning publisher’s policy data

Journal Level Data – The Problems Publishers’ policies may differ by journal – General policy insufficient Multiple or joint publishers – e.g. “Published by … on behalf of …” – If policies differ, whose take priority? Journal listed in two or more sources – Problems equating name variations – Out of date data in secondary databases – Misattribution of journals to publishers

Journal Level Data – RoMEO Plan Compiling our own journal database – Journals of publishers listed in RoMEO only – Harvested directly from publishers’ websites – Including extra fields – e.g. ESSN, alt. titles, etc. – ‘Trust’ order: RoMEO  DOAJ  Zetoc Timescale – Harvesting in progress: >12k of expected 18k titles – Release Autumn 2010

Journal Level Data – Publisher Issues Many journals have more than one ‘publisher’ – E.g. Commercial publisher  Society’s journal – Often not clear in sources who controls rights Each publisher assigned to a hierarchical list – E.g. Copyright holder, Client organisation, Commercial publisher, etc. Need for rules and guidance on precedence – Warnings to users in RoMEO on assumptions

RoMEO Hierarchy of Publisher Types University/Commercial/Governmental Publisher Imprint Associate Organisation Client Organisation Society Publisher Co-publisher Primary Co-publisher Sub-Imprint Special List Independent Journal Copyright Holder

Working Prototype New RoMEO (still under development)

“Official journal of the German Cardiac Society”

API Implications– Journal Queries Current V.2.* Query Options – Unaffected Potential New V.3 Query Options – Finding all journals? – Finding the journals of a specified publisher? – Follow-up by RoMEO or DOAJ journal ID – Etc.

API Implications– Extra Journal Data Current V.2.* XML Schema – Some could go into existing publisher elements E.g. Alternative titles into E.g. Journal home page URL into – Some new data would be lost New V.3 XML Schema – New schema with extra elements and attributes – Some elements initially blank Ready for future population with data

Publisher Data – The Problems Variability of RoMEO phrases & statements – Currently reflect publishers policies – General need for greater clarity Especially “Pre-print” & “Post-print” terminology – Obstacle for translation into other languages Authority of policy statements RoMEO Colours – Often misinterpreted by users

Publisher Data – RoMEO Plan Simpler clearer terminology – E.g. New version terminology Pre-print  Author’s submitted version Post-print  Author’s accepted version More standardised data – Structured data Defined using pick lists, checkboxes, etc – Stored as codes or mnemonics Translations in various languages – Non-standard phrases In English and any native language

Publisher Data – RoMEO Plan Authority of each statement – Link or ref. to the relevant publisher’s source Retaining change history Extra fields - e.g. – Publisher’s home country – Prices of Paid OA options – Publisher’s contact details [Data protection issues] Multilingual interfaces Revise the RoMEO colour scheme?

Idea for Revising RoMEO Colours Green – Can archive Publisher’s version/PDF Blue – Can archive Author’s accepted version Yellow – Can archive Author’s submitted version White – Cannot archive any version Grey – Policies not known (e.g. for a publisher’s client ) Pale shade if permission has embargo or restrictions What about open access journals – ‘Gold’?

API Implications – Publisher Queries Current V.2.* Query Options – Unaffected Potential New V.3 Query Options – Finding non-RoMEO publishers? – Finding publishers’ clients? – Journals produced by a specified publisher? – Etc.

API Implications – V.2.* XML Schema Could the V.2.* schema be extended? – Possibly new elements for totally new fields – … if they do not break user’s applications? – Not for Publisher’s version/PDF Publisher’s version/PDF data – Needs to re-merged back with post-print data New fields and data – Some could go into existing publisher elements – Some new data would be lost

API Implications – New V.3 Schema Radically re-structured data Completely new schema – Not just enhancements to the V.2.* schema New common attributes – ‘la’ = ISO code for language of the data – ‘code’ = Mnemonic codes for RoMEO statements – ‘sourcenum’ = Authority number for a statement Some elements initially blank – Ready for future population with data

Data Migration Initial like-to-like migration to new fields Publisher’s version/PDF – Permanently parsed into new fields Sources for policy statements – Initially set to “Original RoMEO data” Review of all existing RoMEO publishers – Major publishers first – Add data for new fields – Identify specific sources for all statements

Any Questions? RoMEO: API: Blog: Peter Millington: