1. Schema changes
- The key for
ds_metadata
in the dataset will now use dataset IDs (unique identifiers for each dataset version in the Dataverse system). Example:
# Old version
"doi:10.5072/FK2/DUGFC4": { # datasetPersistentId
"status": "OK",
"data": {
"id": 850,
"datasetId": 2663,
"datasetPersistentId": "doi:10.5072/FK2/DUGFC4",
...
# New version
{
"2663": { # datasetId
"status": "OK",
"data": {
"id": 850,
"datasetId": 2663,
"datasetPersistentId": "doi:10.5072/FK2/DUGFC4",
...
ds_metadata_yyyymmdd-HHMMSS.json
now contains data
, path_info
and permission_info
at the second-level.
{
...
"status": "OK",
"data": {
...
},
"path_info": {
...
},
"permission_info": {
...
},
- Changes to the following fields in
path_info
for consistency with the new schema:
collection_alias -> CollectionAlias
collection_id -> CollectionID
pid -> datasetPersistentId
ds_id -> datasetId
path_ids -> path_ids
# Old version
...
"path_info": {
"collection_alias": "toronto",
"collection_id": 22,
"pid": "doi:10.5072/FK2/DUGFC4",
"ds_id": 2663,
"path": "/Nick Field Dataverse",
"path_ids": [
2641
]
}
# New version
...
"path_info": {
"CollectionAlias": "toronto",
"CollectionID": 22,
"datasetPersistentId": "doi:10.5072/FK2/DUGFC4",
"datasetId": 2663,
"path": "/Nick Field Dataverse",
"pathIds": [
2641
]
}
2. Feature updates
- Comibed the representation (
-d
) and permission (-p
) metadata into ds_metadata_yyyymmdd-HHMMSS.json
as a single JSON file.
- Added the following permission roles count of dataset (
DS_Collab
, DS_Admin
, DS_Contrib
, DS_ContribPlus
, DS_Curator
, DS_FileDown
, DS_Member
) for spreadsheet output - Only available if -p
is enabled
3. Bug Fixes
- Corrected spelling mistakes in the README file.
- Restored missing fields for representation metadata in the spreadsheet:
TermsOfUse
CM_AuthorAff
CM_TimeEnd
CM_CollectionStart
CM_CollectionEnd
- Fixed handling
-f
responses with None
objects.