Hi,
One of the current limitations of GeoNode is that you cannot bundle a set of datasets/documents into one research object entity. Looking at other data portals like CKAN or OpenAgrar (MyCORE), you can describe a dataset which consists of multiple files/resources. Here are two examples:
https://demo.ckan.org/dataset/sample-dataset-1
https://www.openagrar.de/receive/openagrar_mods_00054877
The latter example on a GeoNode instance:
https://atlas.thuenen.de/layers/geonode_data_ingest:geonode:bze_lw_standorte_verschleiert
Were the additional files are linked as documents:
There is a GeoNode developer workshop creating a so-called GeoCollection object to link multiple GeoNode ResourceBase objects together: https://docs.geonode.org/en/master/devel/workshops/index.html#create-your-own-django-app
My idea is to build on top of this concept and try to implement RO-Crate as a collection object: https://www.researchobject.org/ro-crate/
RO-Crates do use a metadata JSON to describe the Crate: https://www.researchobject.org/ro-crate/1.1/root-data-entity.html
In this JSON, datasets can be defined as web resources: https://www.researchobject.org/ro-crate/1.1/data-entities.html#web-based-data-entities
Most (all?) of the listed attributes of those datasets can be read by the GeoNode API for the bundled resources. Therefore, you only need to describe the ROCrate bundle itself.
What do the others think about that?
Hi,
One of the current limitations of GeoNode is that you cannot bundle a set of datasets/documents into one research object entity. Looking at other data portals like CKAN or OpenAgrar (MyCORE), you can describe a dataset which consists of multiple files/resources. Here are two examples:
https://demo.ckan.org/dataset/sample-dataset-1
https://www.openagrar.de/receive/openagrar_mods_00054877
The latter example on a GeoNode instance:
https://atlas.thuenen.de/layers/geonode_data_ingest:geonode:bze_lw_standorte_verschleiert
Were the additional files are linked as documents:
There is a GeoNode developer workshop creating a so-called GeoCollection object to link multiple GeoNode ResourceBase objects together: https://docs.geonode.org/en/master/devel/workshops/index.html#create-your-own-django-app
My idea is to build on top of this concept and try to implement RO-Crate as a collection object: https://www.researchobject.org/ro-crate/
RO-Crates do use a metadata JSON to describe the Crate: https://www.researchobject.org/ro-crate/1.1/root-data-entity.html
In this JSON, datasets can be defined as web resources: https://www.researchobject.org/ro-crate/1.1/data-entities.html#web-based-data-entities
Most (all?) of the listed attributes of those datasets can be read by the GeoNode API for the bundled resources. Therefore, you only need to describe the ROCrate bundle itself.
What do the others think about that?