PIDs in the DINI certificate

This year, the DINI working group Electronic Publishing is participating in the PIDapalooza for the first time. This is THE event about persistent identifiers. The session – conducted by the WG speakers Isabella, Paul, Daniel and Thomas – is about the use of PIDs in the DINI Certificate for Open Access Repositories and Publication Services 2019.

„You can calculate with the DINI AG E-Pub.“ (Daniel – one of our WG speaker said about about DINI’s participation in the event)

More information about the event: https://sched.co/gD27

Welcome to the DINI stage! Join us when we go backstage to find out about how PIDs shape the character of the „2019 DINI Certificate for Open Access Publication Services“. Since 2003 six editions of this hot and high quality standard for open access repositories and journals and around 100 institutions in Germany went wild to get it. After this short backstage visit which gives an intro to DINI, the German Initiative of Networked Information, the DINI Certificate will do a stage dive into the session crowd presenting all its songs (requirements and recommendations) that deal with PIDs. In a discursive jam session all party people (virtually) shout out their opinion on these criteria by either celebrating or throwing tomatoes. The remains of the party are swept together and written down in an after party blog post.

What has happened on Twitter so far (more will follow @DiniAgE_Pub):

Zitiervorschlag

Beucke, Daniel. „PIDs in the DINI Certificate.” Blog der DINI AGs FIS & EPUB, 2021. https://doi.org/10.57689/DINI-BLOG.20210125.


Dieser Beitrag ausgenommen Zitate und anderweitig gekennzeichnete Teile ist lizenziert unter der Creative Commons Namensnennung 4.0 International Lizenz (CC BY 4.0).
Creative Commons Lizenzvertrag


Über Daniel Beucke

Daniel arbeitet an der Niedersächsischen Staats- und Universitätsbibliothek Göttingen in der Gruppe Elektronisches Publizieren. Er ist Mitglied in der DINI AG FIS und in der DINI AG E-Pub.

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert