Bethany Seeger (Dec 19 2024 at 14:16): Bethany Seeger (Dec 19 2024 at 14:16):Hello,
I'm working to help map a set of metadata from one system we have into Dataverse. Some of the fields we'd like to use are in the terms[1] category.
Most of the metadata so far, except system fields, are part of a metadata block. It appears that the terms metadata are built in. Is that correct?
Mostly I'm trying to get a handle on what fields come from where and who can manage them (for example, what are system managed fields that we cannot edit?). It seems that these term fields are defined in a different way, but are fields we can and will use to manage licensing/etc? Could I think of these as Dataverse's base metadata data model (along with system managed fields) and all the metadata blocks are adding on to this?
Thanks!
[1] terms tab in https://docs.google.com/spreadsheets/d/1VAhZ83hKURX_4T-bOkn7XCb9h62Gr2gcJI1fWe4Rl4c/edit?gid=1217395969#gid=1217395969
Philip Durbin 🚀 (Dec 19 2024 at 14:18):Right, terms are not in metadata blocks.
Philip Durbin 🚀 (Dec 19 2024 at 14:18):Licenses can be dynamic, if that helps. You can add as many as you want. But other terms are more or less built in or hard coded, as you say.
Philip Durbin 🚀 (Dec 19 2024 at 14:19):You might find this database table helpful: https://guides.dataverse.org/en/6.5/schemaspy/tables/termsofuseandaccess.html
Philip Durbin 🚀 (Dec 19 2024 at 14:20):And I'm glad you found that crosswalk. @Julian Gautier maintains it and might have some thoughts on all this.
Bethany Seeger (Dec 19 2024 at 14:39):Thanks, Phil!
The crosswalk has been very helpful and I'm grateful to @Julian Gautier for maintaining it.
Thank you for the database table link - that is really helping me see how the objects in the system fit together.
Julian Gautier (Dec 19 2024 at 19:26):Glad the crosswalk's helpful Bethany!
Think any other "system generated" metadata should be added to the spreadsheet's second tab?
Last updated: Nov 01 2025 at 14:11 UTC