File Page needs a Term Tab to define terms at the file level

[shlake]

Now that there is a separate files page & in a future release of dataverse each file is going to have its own DOI, the files page needs a Terms Tab.

Main reason for this is to give more information for Restricted files.

It is sort of related to this issue: #3997
which talks about needing more restricted file information, such that a log in is needed.

Maybe a Terms tab on the Files page would be a resolution to issue #3997 ?

[mheppler]

This issue seems like the most logical place to drop a reminder to look into improving the performance of the file pg, as noted in File page - slow/excessive queries (regressive*) #3960. Before we add more features to this page, we should review and refactor as much of the existing code as possible to make sure we are not adding excessive burden to a page that is already under performing.

[TaniaSchlatter]

Sonia also has use cases for this feature. Some Murray datasets have different terms of use for different files in a dataset.

[TaniaSchlatter]

@shlake @adam3smith, our understanding after discussion is that this issue is about displaying terms that apply to a file on the file page. There is no new functionality requested. Is this correct? This issue suggests having the info in a Terms tab on the file page, and @adam3smith requested having it on the metadata tab in #3997.

[shlake]

@TaniaSchlatter

What I think I really wanted when I opened this issue was to have the ability (with a "term tab" on the file page) to be able to set different terms of use per file in the same dataset.

This is what I would like to see, and I thought there was an issue about this: to have an option to set terms/license per file OR at dataset level, but I can't seem to find it now.

But if this issue is about showing the file "terms" of use on the file page - it doesn't matter if it is a separate tab (which the way it reads is this issue) or in the file metadata #3997

[TaniaSchlatter]

Thanks for clarifying, @shlake. The ability to define terms for files will happen with the DataTags integration #871.

[adam3smith]

I also want per-file terms, but the linked issue I opened was indeed just for displaying terms on the file landing page, no additional functionality. That would already help us plenty.

[philippconzett]

I'd like to revive the discussion about file-level license support. I think the topic was first introduced in this Google Group discussion thread and has since been discussed in different settings.

Together with multiple license support (see current support and issue), file-level license support is crucial for a repository to align with the FAIR principles.

Considering how licensing information is provided to DataCite (see, e.g., this question in the PID Forum) and other relevant services, file-level license support is related to the way file-level metadata information is coded; see #5086.

A possible implementation could thus look like this:

• Each file in a dataset needs to be assigned a standard license or customized terms of use.
• The dataset itself or the metadata record describing the entire dataset - if you want - is assigned the CC0 waiver accompanied by the community norm reminder to always cite your sources. See Metadata licensing #6888.

[LauraHuisintveld]

@philippconzett and others: We are also very interested in having licence and access information at file level. This information should be machine-readable, so I agree that having this in the metadata-export(s) is crucial. We (DANS) are participating in a national project, in which we could probably try to spend some time to take a look at this.

[cmbz]

2024/09/09: Keeping, still high level of interest.