Speaker
Description
Most scientific organizations have established bibliographic databases to collect and present the scholarly output generated by their researchers and research projects. Additional requirements arise from increasing OpenAccess requirements by funders more and more paired with direct data delivery (e.g. Horizon 2020). To alleviate the burden of administrative reporting JOIN² has broadened the scope of traditional OpenAccess repositories to include these additional, administrative data like funding, licencing, cost information (e.g. APC based Gold OpenAccess). Recent developments include DOI minting via DataCite and ORCiD integration.
However, to fulfill 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 data schema, JOIN² repositories implemented this normalization based on authority records right from the start. To this end JOIN² 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 site implementations in production, for JOIN² 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, JOIN² is currently investigating the bibliographic subset of the upcoming national German evaluation schema Kerndatensatz Forschung (KDSF). Though, JOIN² was designed long before the discussion on this schema started, it turned out that almost all criteria can be met out of the box by means of JOIN²'s authority control mechanisms, while trouble usually results from flaws in the KDSF defintions 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 JOIN² partners as well as some usage scenarios implemented.
