Closed phette23 closed 4 months ago
Resource Types are the most prominent search filter. Subtype filters appear nested under their parent. RTs do not provide custom fields based on their values (but we should research implementing this with custom fields). The various props
of a RT are all for metadata crosswalks/citations under an item's Export menu.
Invenio's defaults (these are loaded if you do not specify your own): https://github.com/inveniosoftware/invenio-rdm-records/blob/master/invenio_rdm_records/fixtures/data/vocabularies/resource_types.yaml
The quantity of work types in VAULT, as measured by the values of metadata fields local/courseWorkType, local/workType, local/courseWorkTypeSpecific is staggering. We probably cannot support that many. What does CCA need?
tags
which prevents it from showing up on the deposit form but retains it as a search facetQuestions / other possibilities:
We want more subtypes of publication and image, won't use software. Undecided about a "Course Work" type (because it would overlap with all the other types) so we may need to do a trial run.
https://inveniordm.docs.cern.ch/customize/vocabularies/resource_types/
https://discord.com/channels/692989811736182844/724974365451747329/1065248477505929246
Part of this (maybe a blocking sub-issue?) is deciding what our resource types will be. Invenio resource types don't seem to imply a whole lot, they do not come with their own sets of metadata fields.