-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
records: define wanted export formats #1324
Comments
JSON-LD says @ArtemisLav |
JSON-LD export is obviously good to offer, but we would still have to decide on which ontologies or vocabularies we would use in its context. For example, do we want to offer FOAF to describe authors, or INSPIRE author schema, or somesuch? For datasets, shall we use strict DCAT, or Research Objects, or something else? Or shall we simply use only our own custom schemas? That could be another standalone ticket that "only" need implementation once we decide about our own data model. In other words, in this ticket, I was concerned mostly about which kind of already-existing external schemas we think we would like to support, hence how do we serialise our internal format to the outside world... |
Example: Frictionlessdata? See e.g. the RDA standard list at http://rd-alliance.github.io/metadata-directory/standards/ |
schema.org for Google dataset search: https://research.googleblog.com/2017/01/facilitating-discovery-of-public.html |
Some additional info from FREYA/Datacite:
|
Let's go then for:
This is exactly what Zenodo did. |
Closing the RFC. |
In COD2, the records were coded in MARC and could have been easily exported into a plethora of formats supported by Invenio (Dublin Core, RefWorks, EndNote...).
In COD3, the records will be coded in custom JSON Schema formats (see #1312). We shall have to write custom serialisers from JSON to any wanted export format we would like to offer.
This RFC is about which export formats we would like offer in addition to JSON to our end users. For example:
Any suggestions?
The text was updated successfully, but these errors were encountered: