Specify data usage restrictions implementation

legumeinfo / datastore-specifications

Specifications for directory naming, file naming, file contents in the LIS datastore

2 stars 0 forks source link

Specify data usage restrictions implementation #25

Open sammyjava opened 2 years ago

sammyjava commented 2 years ago

We need a robust way of stating the usage restrictions for a non-public data collection.

Requirements (disagree, or add to this list if you see fit):

simple flag in README like license: restricted
text file with full restricted-usage text, presumably in the collection itself, or maybe boilerplate depending on license value? Must be added to the datastore-metadata repo for downstream use
implement into python script that populates _data on website (easy with restricted-usage text available)
implement into h5ai script on Datastore collection view itself (maybe a popup dialog?)

sammyjava commented 2 years ago

@adf-ncgr @nathanweeks @cann0010 I self-assigned this since I've been specifying the Datastore, but feel free to take over this assignment if you so wish. It'll be a collaborative project, methinks, in any case.

sammyjava commented 2 years ago

@adf-ncgr sez:

I should probably note that much of the data we bring in from Phytozome is under similar usage restriction. See species browser at https://phytozome-next.jgi.doe.gov/ and look for RST vs UNRST icons. I suppose that we ought to be copying into place the usage agreements when we grab such datasets- I think sometimes we do, sometimes we indicate that there is a usage agreement in the license but don't specify explicitly what it is. Whenever we get the new approach to this settled, I can try to clean this up.