Skip to main content

Notice

We are in the process of rolling out a soft launch of the RDA website, which includes a new member platform. Existing RDA members PLEASE REACTIVATE YOUR ACCOUNT using this link: https://rda-login.wicketcloud.com/users/confirmation. Visitors may encounter functionality issues with group pages, navigation, missing content, broken links, etc. As you explore the new site, please provide your feedback using the UserSnap tool on the bottom right corner of each page. Thank you for your understanding and support as we work through all issues as quickly as possible. Stay updated about upcoming features and functionalities: https://www.rd-alliance.org/rda-web-platform-upcoming-features-and-functionalities/

#129499

Dear Hugh, Roberto, Andi and Mark,

thank you very much for your thoughts, comments and pointers to other recommendations. They do provide some useful information to consider for shaping BibLaTeX’s @dataset type.

I feel that I should elaborate a bit on my use case to clarify what I am trying to achieve. The repository hosts data from the (digital) humanities, with collections from disciplines like oriental studies, archaeology or history. Sizes of the collections vary significantly (1GB to 10TB; or a few up to 100 000 (and more) resources) and a collection can contain multiple resource types (we use a vocabulary based on DCMI type). We developed a dedicated metadata schema to describe the objects both on collection as well as on resource level and as long as the resources are publicly accessible they also get a PID (Handle). The PID points to the respective object’s landing page with all its metadata and machine-readable endpoints are also available.

To aid in proper attribution when a collection (or a subcollection or a single resource) is re-used the repository provides a citation suggestion. This is comparable to those you can e.g. find on Zenodo or on Dataverse instances. The suggested citation is automatically computed from the metadata and we decided to provide it in BibLaTeX format because most reference management software supports this and also many citation styles already exist.

During the mapping process of our metadata to BibLaTeX, I found that most of the principles of this WG’s recommendations can be met, but not all. As BibLaTeX is still actively developed I saw the chance to shape the @dataset type into something that could then help citation style developers to provide sound and useful citations of ‘datasets’. One of the developers pointed out: “I realise that with some things we might have a bit of a chicken-or-egg problem: Certain things might not be popular yet, because they are not properly supported by the software yet.” — By working on enhancing the data model for the @dataset type and possibly even introduce a new type like @datasubset we could pave the way for better citation styles for data. I myself e.g. was thinking of promoting this in the German-speaking Archaeology community, but this only makes sense if the technological basis is there.

Best
Martina