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
There are two different types of "private" data we have encountered:
Data that's yet not published (e.g. ODUM's curation workflow)
Published data that's available by request or via API key (e.g. some datasets in DV, Kyle B's archaeology Tale)
In 1) I'd propose to register data in a private folder that's owned by admin and read-only for user doing the registration to avoid accidentally exposing data info. In 2) data can be registered as usual as metadata (file names/sizes etc) is publicly available either way, it's only the content that's access protected.
The text was updated successfully, but these errors were encountered:
Rationale
There are two different types of "private" data we have encountered:
In 1) I'd propose to register data in a private folder that's owned by admin and read-only for user doing the registration to avoid accidentally exposing data info. In 2) data can be registered as usual as metadata (file names/sizes etc) is publicly available either way, it's only the content that's access protected.
The text was updated successfully, but these errors were encountered: