Domain
-
keyproject
-
pathproject
-
keyacronym
-
pathproject/acronym
-
commentShort project title, added for the text field "Action Acronym", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keyadditional_rdm_policy
-
pathproject/additional_rdm_policy
-
keyrequirements
-
pathproject/additional_rdm_policy/requirements
-
keyyesno
-
pathproject/additional_rdm_policy/yesno
-
keycoordination
-
pathproject/coordination
-
keyname
-
pathproject/coordination/name
-
keycosts
-
pathproject/costs
-
keycreation
-
pathproject/costs/creation
-
keynon_personnel
-
pathproject/costs/creation/non_personnel
-
keypersonnel
-
pathproject/costs/creation/personnel
-
keyipr
-
pathproject/costs/ipr
-
keyipr_differences
-
pathproject/costs/ipr/ipr_differences
-
keynon_personnel
-
pathproject/costs/ipr/non_personnel
-
keypersonnel
-
pathproject/costs/ipr/personnel
-
keymetadata
-
pathproject/costs/metadata
-
keydifferences
-
pathproject/costs/metadata/differences
-
keynon_personnel
-
pathproject/costs/metadata/non_personnel
-
keypersonnel
-
pathproject/costs/metadata/personnel
-
keyother_research_output
-
pathproject/costs/other_research_output
-
keynon_personnel
-
pathproject/costs/other_research_output/non_personnel
-
commentAdded for the question about costs associated with other research output, required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keypersonnel
-
pathproject/costs/other_research_output/personnel
-
commentAdded for the question about costs associated with other research output, required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keypid
-
pathproject/costs/pid
-
keynon_personnel
-
pathproject/costs/pid/non_personnel
-
keypersonnel
-
pathproject/costs/pid/personnel
-
keypid_costs_differences
-
pathproject/costs/pid/pid_costs_differences
-
keypreservation
-
pathproject/costs/preservation
-
keycosts_differences
-
pathproject/costs/preservation/costs_differences
-
keycover_how
-
pathproject/costs/preservation/cover_how
-
keynon_personnel
-
pathproject/costs/preservation/non_personnel
-
keypersonnel
-
pathproject/costs/preservation/personnel
-
keysensitive_data
-
pathproject/costs/sensitive_data
-
keyanonymization
-
pathproject/costs/sensitive_data/anonymization
-
keynon_personnel
-
pathproject/costs/sensitive_data/anonymization/non_personnel
-
keypersonnel
-
pathproject/costs/sensitive_data/anonymization/personnel
-
keycosts_differences
-
pathproject/costs/sensitive_data/costs_differences
-
keysecurity
-
pathproject/costs/sensitive_data/security
-
keynon_personnel
-
pathproject/costs/sensitive_data/security/non_personnel
-
keypersonnel
-
pathproject/costs/sensitive_data/security/personnel
-
keystorage
-
pathproject/costs/storage
-
keynon_personnel
-
pathproject/costs/storage/non_personnel
-
keypersonnel
-
pathproject/costs/storage/personnel
-
keyusage
-
pathproject/costs/usage
-
keydifferences
-
pathproject/costs/usage/differences
-
keynon_personnel
-
pathproject/costs/usage/non_personnel
-
keypersonnel
-
pathproject/costs/usage/personnel
-
keydata_management
-
pathproject/data_management
-
keyname
-
pathproject/data_management/name
-
keydataset
-
pathproject/dataset
-
keycollaboration_organisation
-
pathproject/dataset/collaboration_organisation
-
keycollaboration_tools
-
pathproject/dataset/collaboration_tools
-
keycollaboration_yesno
-
pathproject/dataset/collaboration_yesno
-
keycontrol_tool
-
pathproject/dataset/control_tool
-
keycreation_methods
-
pathproject/dataset/creation_methods
-
keycreator
-
pathproject/dataset/creator
-
keyname
-
pathproject/dataset/creator/name
-
keycuration
-
pathproject/dataset/curation
-
keyresponsible_person
-
pathproject/dataset/curation/responsible_person
-
keyname
-
pathproject/dataset/curation/responsible_person/name
-
keydata_analysis_end
-
pathproject/dataset/data_analysis_end
-
keydata_analysis_start
-
pathproject/dataset/data_analysis_start
-
keydata_cleansing_end
-
pathproject/dataset/data_cleansing_end
-
keydata_cleansing_start
-
pathproject/dataset/data_cleansing_start
-
keydata_collection_end
-
pathproject/dataset/data_collection_end
-
keydata_collection_start
-
pathproject/dataset/data_collection_start
-
keydata_date_difference
-
pathproject/dataset/data_date_difference
-
keydata_publication_date
-
pathproject/dataset/data_publication_date
-
keydata_publication_pid
-
pathproject/dataset/data_publication_pid
-
keydata_security
-
pathproject/dataset/data_security
-
keyaccess_permissions
-
pathproject/dataset/data_security/access_permissions
-
keybackup_responsible
-
pathproject/dataset/data_security/backup_responsible
-
keyname
-
pathproject/dataset/data_security/backup_responsible/name
-
keybackups
-
pathproject/dataset/data_security/backups
-
keyrisks
-
pathproject/dataset/data_security/risks
-
keysecurity_measures
-
pathproject/dataset/data_security/security_measures
-
keydescription
-
pathproject/dataset/description
-
keydocumentation
-
pathproject/dataset/documentation
-
commentAdded for the question which documentation will be available together with the data
-
keywhere
-
pathproject/dataset/documentation/where
-
commentAdded for the question where the documentation can be found
-
keydocumentation_on_request
-
pathproject/dataset/documentation_on_request
-
commentAdded for the question "Which data documention is only available on request?" The question was of relevance for DFG projects in educational research until 2021, see Petra Stanat, Bereitstellung und Nutzung quantitativer Forschungsdaten in der Bildungsforschung: Memorandum des Fachkollegiums "Erziehungswissenschaft" der DFG, 2015, https://www.dfg.de/download/pdf/foerderung/grundlagen_dfg_foerderung/forschungsdaten/richtlinien_forschungsdaten_bildungsforschung.pdf.
-
keyformat
-
pathproject/dataset/format
-
keyid
-
pathproject/dataset/id
-
commentShort ID for a dataset, used as questionset attribute for dataset related questionsets.
-
keyinclude_software
-
pathproject/dataset/include_software
-
keyintegration
-
pathproject/dataset/integration
-
keyinteroperability
-
pathproject/dataset/interoperability
-
keyipr
-
pathproject/dataset/ipr
-
keycopyrights
-
pathproject/dataset/ipr/copyrights
-
keyother_rights
-
pathproject/dataset/ipr/other_rights
-
keyowner
-
pathproject/dataset/ipr/owner
-
keyname
-
pathproject/dataset/ipr/owner/name
-
keystatus
-
pathproject/dataset/ipr/status
-
commentIn the "Information for Building Language Corpora Under German Law" of the DFG Review Board on Linguistics, https://www.dfg.de/download/pdf/foerderung/antragstellung/forschungsdaten/guidelines_review_board_linguistics_corpora.pdf, is explicitly pointed to single rights of the originator and the necessity to obtain these rights. For the question "Which rights have been obtained or what is the status of the rights collection?" this attribute has been added.
-
keymetadata
-
pathproject/dataset/metadata
-
keyaccess_info
-
pathproject/dataset/metadata/access_info
-
commentAdded for the question "Will metadata contain information to enable the user to access the data?", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keyavailable_without_data
-
pathproject/dataset/metadata/available_without_data
-
commentAdded for the question "Will metadata be guaranteed to remain available after data is no longer available?", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keycreation
-
pathproject/dataset/metadata/creation
-
keycreation_automatic
-
pathproject/dataset/metadata/creation_automatic
-
keycreation_manual
-
pathproject/dataset/metadata/creation_manual
-
keycreation_semi_automatic
-
pathproject/dataset/metadata/creation_semi_automatic
-
keyharvesting
-
pathproject/dataset/metadata/harvesting
-
commentAdded for the question "Will metadata be offered in such a way that it can be harvested and indexed?", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keylicense_for_metadata
-
pathproject/dataset/metadata/license_for_metadata
-
commentAdded for the question "Will metadata be made openly available and licenced under a public domain dedication CC0, as per the Grant Agreement? If not, please clarify why.", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keymappings
-
pathproject/dataset/metadata/mappings
-
keypublic
-
pathproject/dataset/metadata/public
-
keyquality_assurance
-
pathproject/dataset/metadata/quality_assurance
-
keyreferences_to_other_data
-
pathproject/dataset/metadata/references_to_other_data
-
commentAdded for the question "Will your data include qualified references to other data (e.g. other data from your project, or datasets from previous research)?", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keyresponsible_person
-
pathproject/dataset/metadata/responsible_person
-
keyname
-
pathproject/dataset/metadata/responsible_person/name
-
keyscope
-
pathproject/dataset/metadata/scope
-
keysearch_keywords
-
pathproject/dataset/metadata/search_keywords
-
commentAdded for the question "Will search keywords be provided in the metadata to optimize the possibility for discovery and then potential re-use?", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keystandards
-
pathproject/dataset/metadata/standards
-
keyvocabularies_open
-
pathproject/dataset/metadata/vocabularies_open
-
commentAdded for the question "Will you openly publish the generated ontologies or vocabularies to allow reusing, refining or extending them?", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keymethod
-
pathproject/dataset/method
-
keyorigin
-
pathproject/dataset/origin
-
keypids
-
pathproject/dataset/pids
-
keyresolver
-
pathproject/dataset/pids/resolver
-
commentAdded for the question "Will the repository resolve the identifier to a digital object?", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keyresponsible_person
-
pathproject/dataset/pids/responsible_person
-
keyname
-
pathproject/dataset/pids/responsible_person/name
-
keysubentities
-
pathproject/dataset/pids/subentities
-
keysystem
-
pathproject/dataset/pids/system
-
keyyesno
-
pathproject/dataset/pids/yesno
-
keypreservation
-
pathproject/dataset/preservation
-
keyaccess_authentication
-
pathproject/dataset/preservation/access_authentication
-
keycertification
-
pathproject/dataset/preservation/certification
-
keydata_archiving_date
-
pathproject/dataset/preservation/data_archiving_date
-
keyduration
-
pathproject/dataset/preservation/duration
-
keyembargo_period
-
pathproject/dataset/preservation/embargo_period
-
keyend_date
-
pathproject/dataset/preservation/embargo_period/end_date
-
commentAdded for the question "Wann endet das Embargo?" in DMP4NFDI
-
keystart_date
-
pathproject/dataset/preservation/embargo_period/start_date
-
commentAdded for the question "Wann beginnt das Embargo?" in DMP4NFDI
-
keypurpose
-
pathproject/dataset/preservation/purpose
-
keyrepository
-
pathproject/dataset/preservation/repository
-
keyrepository_arrangements
-
pathproject/dataset/preservation/repository_arrangements
-
keyresponsible_person
-
pathproject/dataset/preservation/responsible_person
-
commentRefers to the permanent project owner: see https://github.com/rdmorganiser/rdmo-catalog/issues/110
-
keyemail
-
pathproject/dataset/preservation/responsible_person/email
-
commentRefers to the permanent project owner: see https://github.com/rdmorganiser/rdmo-catalog/issues/110
-
keyname
-
pathproject/dataset/preservation/responsible_person/name
-
commentRefers to the permanent project owner: see https://github.com/rdmorganiser/rdmo-catalog/issues/110
-
keyreuse_duration
-
pathproject/dataset/preservation/reuse_duration
-
keytrusted
-
pathproject/dataset/preservation/trusted
-
commentAdded for the question "Will the data be deposites in a trusted repository?", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keyyesno
-
pathproject/dataset/preservation/yesno
-
keyprovenance
-
pathproject/dataset/provenance
-
keycontent
-
pathproject/dataset/provenance/content
-
commentAdded for the question "What is the provenance of the data?", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keystandards
-
pathproject/dataset/provenance/standards
-
commentAdded for the question "Will the provenance of the data be thoroughly documented using the appropriate standards?", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keyquality_assurance
-
pathproject/dataset/quality_assurance
-
keyrate
-
pathproject/dataset/rate
-
keyreproducibility
-
pathproject/dataset/reproducibility
-
keyreuse_existing
-
pathproject/dataset/reuse_existing
-
commentAdded for the purpose of stating the reasons "if re-use of any existing data has been considered but discarded". EU Horizon Europe requires suggestions concerning this question, see Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keyreuse_scenario
-
pathproject/dataset/reuse_scenario
-
keyreuse_scenario_usage
-
pathproject/dataset/reuse_scenario_usage
-
keysensitive_data
-
pathproject/dataset/sensitive_data
-
keyother
-
pathproject/dataset/sensitive_data/other
-
keydescription
-
pathproject/dataset/sensitive_data/other/description
-
keyyesno
-
pathproject/dataset/sensitive_data/other/yesno
-
keypersonal_data
-
pathproject/dataset/sensitive_data/personal_data
-
keyanonymization
-
pathproject/dataset/sensitive_data/personal_data/anonymization
-
keybdsg_3_9
-
pathproject/dataset/sensitive_data/personal_data/bdsg_3_9
-
keyconsent
-
pathproject/dataset/sensitive_data/personal_data/consent
-
keyextent
-
pathproject/dataset/sensitive_data/personal_data/consent/extent
-
keyrecord
-
pathproject/dataset/sensitive_data/personal_data/consent/record
-
keystatement
-
pathproject/dataset/sensitive_data/personal_data/consent/statement
-
keydeletion
-
pathproject/dataset/sensitive_data/personal_data/deletion
-
keypersonal_data_yesno
-
pathproject/dataset/sensitive_data/personal_data_yesno
-
keyyesno
-
pathproject/dataset/sensitive_data/personal_data_yesno/yesno
-
keysharing
-
pathproject/dataset/sharing
-
keyconditions
-
pathproject/dataset/sharing/conditions
-
keyexplanation
-
pathproject/dataset/sharing/explanation
-
keyfindability
-
pathproject/dataset/sharing/findability
-
keyrepository
-
pathproject/dataset/sharing/repository
-
commentRefers to the place of publication, which must be distinguished from the place of storaging and archiving (see https://github.com/rdmorganiser/rdmo-catalog/issues/55)
-
keyrestrictions_explanation
-
pathproject/dataset/sharing/restrictions_explanation
-
keysharing_license
-
pathproject/dataset/sharing/sharing_license
-
keyuri
-
pathproject/dataset/sharing/uri
-
commentLink zum veröffentlichten Datensatz
-
keyyesno
-
pathproject/dataset/sharing/yesno
-
keysize
-
pathproject/dataset/size
-
keynumber_files
-
pathproject/dataset/size/number_files
-
keyvolume
-
pathproject/dataset/size/volume
-
keysoftware_documentation
-
pathproject/dataset/software_documentation
-
keystorage
-
pathproject/dataset/storage
-
keynaming_policy
-
pathproject/dataset/storage/naming_policy
-
keyorganisation_policy
-
pathproject/dataset/storage/organisation_policy
-
keytype
-
pathproject/dataset/storage/type
-
keyuri
-
pathproject/dataset/storage/uri
-
keystructure
-
pathproject/dataset/structure
-
keytitle
-
pathproject/dataset/title
-
keyuri
-
pathproject/dataset/uri
-
keyusage_description
-
pathproject/dataset/usage_description
-
keyusage_frequency
-
pathproject/dataset/usage_frequency
-
keyusage_infrastructure
-
pathproject/dataset/usage_infrastructure
-
keyusage_support
-
pathproject/dataset/usage_support
-
keyusage_technology
-
pathproject/dataset/usage_technology
-
keygeo_location
-
pathproject/dataset/usage_technology/geo_location
-
commentAdded for the question "Standort des Instruments während der Kampagne" in DMP4NFDI
-
keyversioning_strategy
-
pathproject/dataset/versioning_strategy
-
keyversioning_tool
-
pathproject/dataset/versioning_tool
-
keyversioning_versions_differences
-
pathproject/dataset/versioning_versions_differences
-
keyversioning_yesno
-
pathproject/dataset/versioning_yesno
-
keyvolume_rate_difference
-
pathproject/dataset/volume_rate_difference
-
keydmp
-
pathproject/dmp
-
keydmp_date
-
pathproject/dmp/dmp_date
-
commentDate of this data management plan version, added for the text field "Date", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keydmp_version
-
pathproject/dmp/dmp_version
-
commentVersion of this data management plan, added for the text field "DMP version", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keyname
-
pathproject/dmp/name
-
keyexternal_services
-
pathproject/external_services
-
keyfunder
-
pathproject/funder
-
keygrant_nr
-
pathproject/funder/grant_nr
-
commentAdded for the text field "Action Number", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keyid
-
pathproject/funder/id
-
commentShort ID for a funder, used as questionset attribute for funder related questionsets.
-
keyname
-
pathproject/funder/name
-
keyprogramme
-
pathproject/funder/programme
-
keytitle
-
pathproject/funder/programme/title
-
keyurl
-
pathproject/funder/programme/url
-
keyrdm_policy
-
pathproject/funder/rdm_policy
-
keyyesno
-
pathproject/funder/yesno
-
keylegal_aspects
-
pathproject/legal_aspects
-
keyinternational_yesno
-
pathproject/legal_aspects/international_yesno
-
keyipr
-
pathproject/legal_aspects/ipr
-
keyyesno
-
pathproject/legal_aspects/ipr/yesno
-
keyofficial_approval
-
pathproject/legal_aspects/official_approval
-
keydata_access_committee
-
pathproject/legal_aspects/official_approval/data_access_committee
-
keyethics_committee
-
pathproject/legal_aspects/official_approval/ethics_committee
-
keystatutatory_approval
-
pathproject/legal_aspects/official_approval/statutatory_approval
-
keyagency
-
pathproject/legal_aspects/official_approval/statutatory_approval/agency
-
keyconditions
-
pathproject/legal_aspects/official_approval/statutatory_approval/conditions
-
commentAdded for the question "What are the conditions for the permit?", recommended in Fachkollegium "Alte Kulturen", Handreichung zum Umgang mit Forschungsdaten, 2020, https://www.dfg.de/download/pdf/foerderung/grundlagen_dfg_foerderung/forschungsdaten/handreichung_fachkollegium_101_forschungsdaten.pdf
-
keytitle
-
pathproject/legal_aspects/official_approval/statutatory_approval/title
-
keyyesno
-
pathproject/legal_aspects/official_approval/statutatory_approval/yesno
-
keysensitive_data
-
pathproject/legal_aspects/sensitive_data
-
keyother
-
pathproject/legal_aspects/sensitive_data/other
-
keyyesno
-
pathproject/legal_aspects/sensitive_data/other/yesno
-
keypersonal_data
-
pathproject/legal_aspects/sensitive_data/personal_data
-
keyyesno
-
pathproject/legal_aspects/sensitive_data/personal_data/yesno
-
keyprivacy_law
-
pathproject/legal_aspects/sensitive_data/privacy_law
-
keyyesno
-
pathproject/legal_aspects/sensitive_data/yesno
-
keyother_research_output
-
pathproject/other_research_output
-
commentSome research funders not only expect information about research data in a data management plan. Other research output can be digital as software, workflows and models, or physical as new materials, antibodies, reagents, samples, etc.
-
keyfair
-
pathproject/other_research_output/fair
-
commentIncluded for the Horizon Europe question "Beneficiaries should consider which of the questions pertaining to FAIR data above, can apply to the management of other research outputs, and should strive to provide sufficient detail on how their research outputs will be managed and shared, or made available for re-use, in line with the FAIR principles."
-
keyplan
-
pathproject/other_research_output/plan
-
commentAdded for the question "In addition to the management of data, beneficiaries should also consider and plan for the management of other research outputs that may be generated or re-used throughout their projects. Such outputs can be either digital (e.g. software, workflows, protocols, models, etc.) or physical (e.g. new materials, antibodies, reagents, samples, etc.). Beneficiaries should consider which of the questions pertaining to FAIR data above, can apply to the management of other research outputs, and should strive to provide sufficient detail on how their research outputs will be managed and shared, or made available for re-use, in line with the FAIR principles. ", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keypartner
-
pathproject/partner
-
keyagreement
-
pathproject/partner/agreement
-
keycontact_person
-
pathproject/partner/contact_person
-
keyname
-
pathproject/partner/contact_person/name
-
keyphone
-
pathproject/partner/contact_person/phone
-
keyid
-
pathproject/partner/id
-
commentShort ID for a project partner, used as questionset attribute for project partner related questionsets.
-
keyname
-
pathproject/partner/name
-
keyrdm_policy
-
pathproject/partner/rdm_policy
-
keyresponsibilities
-
pathproject/partner/responsibilities
-
keyphysical_objects
-
pathproject/physical_objects
-
keypreservation
-
pathproject/preservation
-
keyarchive
-
pathproject/preservation/archive
-
keyfair_archive
-
pathproject/preservation/archive/fair_archive
-
keynonprofit
-
pathproject/preservation/archive/nonprofit
-
keyexplanation
-
pathproject/preservation/archive/nonprofit/explanation
-
keyyesno
-
pathproject/preservation/archive/nonprofit/yesno
-
keyyesno
-
pathproject/preservation/archive/yesno
-
keyresponsible_person
-
pathproject/preservation/responsible_person
-
keyname
-
pathproject/preservation/responsible_person/name
-
keyretained
-
pathproject/preservation/retained
-
keyselection_criteria
-
pathproject/preservation/selection_criteria
-
keyselection_format
-
pathproject/preservation/selection_format
-
keyresearch_field
-
pathproject/research_field
-
keytitle
-
pathproject/research_field/title
-
keyresearch_question
-
pathproject/research_question
-
keydate_differences
-
pathproject/research_question/date_differences
-
keykeywords
-
pathproject/research_question/keywords
-
keytitle
-
pathproject/research_question/title
-
keyschedule
-
pathproject/schedule
-
keyproject_end
-
pathproject/schedule/project_end
-
keyproject_start
-
pathproject/schedule/project_start
-
keysupport
-
pathproject/support
-
keycosts
-
pathproject/support/costs
-
keyyesno
-
pathproject/support/yesno
-
keytitle
-
pathproject/title
-
commentFull project title, added for the text field "Action Title", required in the Horizon Europe Data Management Plan Template, 05.05.2021, https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/horizon/temp-form/report/data-management-plan-template_he_en.docx
-
keysmp
-
pathsmp
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyapplication-class
-
pathsmp/application-class
-
keybuy-or-make
-
pathsmp/buy-or-make
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keycoding-standards
-
pathsmp/coding-standards
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keycommunity-requirements
-
pathsmp/community-requirements
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keycontribute-software
-
pathsmp/contribute-software
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keydecision-releasing
-
pathsmp/decision-releasing
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keydevelopment-process
-
pathsmp/development-process
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keydocumentation
-
pathsmp/documentation
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keydocumentation-stored
-
pathsmp/documentation/documentation-stored
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keywho-is-responsible
-
pathsmp/documentation/who-is-responsible
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keydual-use
-
pathsmp/dual-use
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyexternal-components
-
pathsmp/external-components
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyexternal-software-rights
-
pathsmp/external-software-rights
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyfeedback-process
-
pathsmp/feedback-process
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keygovernance-model
-
pathsmp/governance-model
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyinfrastructure-existing
-
pathsmp/infrastructure-existing
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyinfrastructure-required
-
pathsmp/infrastructure-required
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyinstitutional-requirements
-
pathsmp/institutional-requirements
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keylanguage
-
pathsmp/language
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keypeer-review
-
pathsmp/peer-review
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keypreservation
-
pathsmp/preservation
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keypublish-smp
-
pathsmp/publish-smp
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyqualified-references
-
pathsmp/qualified-references
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyre-usable
-
pathsmp/re-usable
-
keyrelation-SMP-DMP
-
pathsmp/relation-SMP-DMP
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyreleasing-who
-
pathsmp/releasing-who
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keysafety
-
pathsmp/safety
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keysecurity
-
pathsmp/security
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keysoftware-license
-
pathsmp/software-license
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keysoftware-metadata
-
pathsmp/software-metadata
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keysoftware-pid
-
pathsmp/software-pid
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keysoftware-property-rights
-
pathsmp/software-property-rights
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keysoftware-repository
-
pathsmp/software-repository
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keysoftware-sharing
-
pathsmp/software-sharing
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyspecification-sheet
-
pathsmp/specification-sheet
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keystore-software
-
pathsmp/store-software
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keysupport-for-software
-
pathsmp/support-for-software
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keytechnical-support
-
pathsmp/technical-support
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keytest-documentation
-
pathsmp/test-documentation
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keytest-strategy
-
pathsmp/test-strategy
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keythird-party-licenses
-
pathsmp/third-party-licenses
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keytrack-external-software
-
pathsmp/track-external-software
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keytrack-tasks
-
pathsmp/track-tasks
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyversioning
-
pathsmp/versioning
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan
-
keyweb-services
-
pathsmp/web-services
-
commentintroduced by the Max Planck Digital Library to implement the Software Management Plan