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
Just a very quick enhancement request, we should discuss options/usefulness.
It'd be great to have the option to create an in-site "corpus homepage" with extended metadata on the selected corpus. Could re-use SaltInfo output and would give end users the opportunity to find out quickly if the corpus in question will be of use to them. Reduces re-duplication of information and infrastructure because you could have everything in one place.
Would need to think about security though, strip JS, etc.
The text was updated successfully, but these errors were encountered:
If I could add input RE: security - one of the main problems we have with corpus navigation is inability of unlogged in users to see that there is a corpus for which they might want to request access (since it is simply not visible if they don't have a right to see it). For this reason, we created this page at GU, which is annoying to maintain:
It would be great if corpus rights management could flag a corpus as 'discoverable', which could work well in conjunction with this feature request: details about the corpus could be revealed in the description tab, although searches would be disabled. Presumably the setting should be combinable with search rights:
Display all corpora the user has a right to
For corpora the user doesn't have access to, allow a flag making them visible/explorable in corpus explorer (but not searchable)
Just a very quick enhancement request, we should discuss options/usefulness.
It'd be great to have the option to create an in-site "corpus homepage" with extended metadata on the selected corpus. Could re-use SaltInfo output and would give end users the opportunity to find out quickly if the corpus in question will be of use to them. Reduces re-duplication of information and infrastructure because you could have everything in one place.
Would need to think about security though, strip JS, etc.
The text was updated successfully, but these errors were encountered: