openMINDS_core
openMINDS_core copied to clipboard
Rediscuss file presentations incl. formalization of access modalities
I would like to rediscuss the way files are represented in openMINDS currently. The following aspects seem to be non-ideal:
- distinction of the location/access url and "file" since the same file could potentially have multiple locations
- properties in file representations which are usually not easily automatically acquired (such as "specialUsageRole", "contentDescription" etc.) should be extracted from the "file" entity to simplify automatic ingestion
- for access protected resources (this is also relevant e.g. for protected web services), we should find a way to formalize the authentication protocols required for such a file so automated pipelines have a chance to execute the proper steps for gathering a valid token and to properly authenticate.
Also in this aspect, we might want to think about how to deal with archives (ZIP / TARs) and/or the "FileArchive" schema
related past issue (closed) #257
I think #318 is also relevant. We probably need a brainstorming meeting to work through all of this.
PS (from @apdavison) this includes also better representations of archived or secondary repositories.