You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the hash included in bag names is used to determine whether an item in figshare has changed and the bag needs to be updated. This has is generated from the entirety of the metadata contained in the JSON response in the Figshare API. To minimize the need to re-bag previously preserved items when the metadata has changed, PR #103 includes a function to sort and standardize the JSON. This issue is to further improve on that by only hashing fields that we care about.
Suggested Implementation
Add another function in Utils.py to calculate a hash based only on certain top-level keys we care about. A suggested list
files
custom_fields (if a new custom field is added, a quick test shows that it does not show up in already-published items)
authors (if an author changes their name or orcid, this is reflected in already-published items)
description
funding_list
version
license
tags
categories
related_materials
title
doi
defined_type_name
timeline
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Description
Currently, the hash included in bag names is used to determine whether an item in figshare has changed and the bag needs to be updated. This has is generated from the entirety of the metadata contained in the JSON response in the Figshare API. To minimize the need to re-bag previously preserved items when the metadata has changed, PR #103 includes a function to sort and standardize the JSON. This issue is to further improve on that by only hashing fields that we care about.
Suggested Implementation
Add another function in Utils.py to calculate a hash based only on certain top-level keys we care about. A suggested list
The text was updated successfully, but these errors were encountered: