Home > Publications database > Normalization and Authority Control in a Repository Landscape |
Poster | PUBDB-2017-05980 |
; ;
2017
This record in other databases:
Please use a persistent id in citations: http://hdl.handle.net/2128/14708 doi:10.15120/GSI-2017-00769 doi:10.3204/PUBDB-2017-05980
Abstract: Most scientific organizations have established bibliographic databases to collect and present the scholarly output generated by their researchers and research projects. Additional requirements arise fromincreasing OpenAccess requirements by funders more and more paired with direct data delivery (e.g. Horizon 2020). To alleviate the burden of administrative reporting JOIN2 has broadened the scope oftraditional OpenAccess repositories to include these additional, administrative data like funding, licencing, cost information (e.g. APC based Gold OpenAccess). Recent developments include DOI minting viaDataCite and ORCiD integration.However, to fulfil all the detailed requirements a very high level of normalization is required, traditionally not available in Dublin Core based repositories. Based on invenio and the much broader Marc21 meta dataschema, JOIN2 repositories implemented this normalization based on authority records right from the start. To this end JOIN2 holds about 118.000 authority records used by and interchanged between all partners.About 72.000 of these refer to scientific journals that need to be updated once a year to reflect changes in statistical keys required for evaluation procedures. Currently operating seven independent, on siteimplementations in production, for JOIN2 it is vitally important to implement a collaborative curation of these records and effective sharing mechanism to minimize the work for partners.For evaluation purposes, JOIN2 is currently investigating the bibliographic subset of the upcoming national German evaluation schema Kerndatensatz Forschung (KDSF). Though, JOIN2 was designed long beforethe discussion on this schema started, it turned out that almost all criteria can be met out of the box by means of JOIN2's authority control mechanisms, while trouble usually results from flaws in the KDSFdefinitions and should be addressed there. Data delivery in CERIF formats may thus be a feature for future implementation.This poster will outline procedures for authority record generation and interchange between JOIN2 partners as well as some usage scenarios implemented.
![]() |
The record appears in these collections: |