https://datacitation.openconcept.no/Recommendations-for-Data-Repositories

Method
GET
HTTP Status
200
IP
141.0.252.107
Profiled on
Token
8c4fb6

ContentController :: dataCitationAction

Request

GET Parameters

No GET parameters

POST Parameters

No POST parameters

Uploaded Files

No files were uploaded

Request Attributes

Key Value
_controller 
"App\Controller\ContentController::dataCitationAction"
_editmode 
false
_event_controller 
App\Controller\ContentController {#1826
  #container: Symfony\Component\DependencyInjection\Argument\ServiceLocator {#1824 …}
}
_locale 
null
_pimcore_context 
"default"
_pimcore_frontend_request 
true
_route 
"document_162"
_route_params 
[
  "_locale" => null
]
_site 
Pimcore\Model\Site {#1555
  #dao: null
  #id: 1
  #domains: [
    ""
  ]
  #rootId: 160
  #rootDocument: Pimcore\Model\Document\Page {#1639 …}
  #rootPath: null
  #mainDomain: "datacitation.openconcept.no"
  #errorDocument: "/Errorpage"
  #localizedErrorDocuments: [
    "en" => "/Errorpage"
  ]
  #redirectToMainDomain: false
  #creationDate: 1738654614
  #modificationDate: 1738654614
  +"____pimcore_cache_item__": "site_domain_a3b0cba464ec7a88803d1807fe2fad3b"
  id: 1
  domains: [
    ""
  ]
  rootId: 160
  rootDocument: Pimcore\Model\Document\Page {#1639 …}
  rootPath: null
  mainDomain: "datacitation.openconcept.no"
  errorDocument: "/Errorpage"
  localizedErrorDocuments: [
    "en" => "/Errorpage"
  ]
  redirectToMainDomain: false
  creationDate: 1738654614
  modificationDate: 1738654614
}
_site_path 
"/Data-Citation/Recommendations-for-Data-Repositories"
_stopwatch_token 
"30cdc5"
_template 
Sensio\Bundle\FrameworkExtraBundle\Configuration\Template {#2559
  #template: "content/data_citation.html.twig"
  -vars: []
  -streamable: false
  -owner: [
    App\Controller\ContentController {#1826
      #container: Symfony\Component\DependencyInjection\Argument\ServiceLocator {#1824 …}
    }
    "dataCitationAction"
  ]
}
contentDocument 
Pimcore\Model\Document\Page {#1894
  #dao: Pimcore\Model\Document\Page\Dao {#3472 …}
  #dependencies: null
  #__dataVersionTimestamp: 1738759478
  #path: "/Data-Citation/"
  #properties: [
    "blog_default_document" => Pimcore\Model\Property {#1891
      #dao: null
      #name: "blog_default_document"
      #data: "51"
      #type: "document"
      #ctype: "document"
      #cpath: null
      #cid: 162
      #inheritable: true
      #inherited: true
      name: "blog_default_document"
      data: "51"
      type: "document"
      ctype: "document"
      cpath: null
      cid: 162
      inheritable: true
      inherited: true
    }
    "event_default_document" => Pimcore\Model\Property {#1885
      #dao: null
      #name: "event_default_document"
      #data: "44"
      #type: "document"
      #ctype: "document"
      #cpath: null
      #cid: 162
      #inheritable: true
      #inherited: true
      name: "event_default_document"
      data: "44"
      type: "document"
      ctype: "document"
      cpath: null
      cid: 162
      inheritable: true
      inherited: true
    }
    "fallback_newsimg" => Pimcore\Model\Property {#1884
      #dao: null
      #name: "fallback_newsimg"
      #data: "488"
      #type: "asset"
      #ctype: "document"
      #cpath: null
      #cid: 162
      #inheritable: true
      #inherited: true
      name: "fallback_newsimg"
      data: "488"
      type: "asset"
      ctype: "document"
      cpath: null
      cid: 162
      inheritable: true
      inherited: true
    }
    "language" => Pimcore\Model\Property {#1879
      #dao: null
      #name: "language"
      #data: null
      #type: "text"
      #ctype: "document"
      #cpath: null
      #cid: 162
      #inheritable: true
      #inherited: true
      name: "language"
      data: null
      type: "text"
      ctype: "document"
      cpath: null
      cid: 162
      inheritable: true
      inherited: true
    }
    "navigation_root" => Pimcore\Model\Property {#1880
      #dao: null
      #name: "navigation_root"
      #data: "1"
      #type: "document"
      #ctype: "document"
      #cpath: null
      #cid: 162
      #inheritable: true
      #inherited: true
      name: "navigation_root"
      data: "1"
      type: "document"
      ctype: "document"
      cpath: null
      cid: 162
      inheritable: true
      inherited: true
    }
    "news_default_document" => Pimcore\Model\Property {#1881
      #dao: null
      #name: "news_default_document"
      #data: "43"
      #type: "document"
      #ctype: "document"
      #cpath: null
      #cid: 162
      #inheritable: true
      #inherited: true
      name: "news_default_document"
      data: "43"
      type: "document"
      ctype: "document"
      cpath: null
      cid: 162
      inheritable: true
      inherited: true
    }
    "project_default_document" => Pimcore\Model\Property {#1882
      #dao: null
      #name: "project_default_document"
      #data: "25"
      #type: "document"
      #ctype: "document"
      #cpath: null
      #cid: 162
      #inheritable: true
      #inherited: true
      name: "project_default_document"
      data: "25"
      type: "document"
      ctype: "document"
      cpath: null
      cid: 162
      inheritable: true
      inherited: true
    }
    "rdresource_default_document" => Pimcore\Model\Property {#1878
      #dao: null
      #name: "rdresource_default_document"
      #data: "159"
      #type: "document"
      #ctype: "document"
      #cpath: null
      #cid: 162
      #inheritable: true
      #inherited: true
      name: "rdresource_default_document"
      data: "159"
      type: "document"
      ctype: "document"
      cpath: null
      cid: 162
      inheritable: true
      inherited: true
    }
    "resource_default_document" => Pimcore\Model\Property {#1876
      #dao: null
      #name: "resource_default_document"
      #data: "6"
      #type: "document"
      #ctype: "document"
      #cpath: null
      #cid: 162
      #inheritable: true
      #inherited: true
      name: "resource_default_document"
      data: "6"
      type: "document"
      ctype: "document"
      cpath: null
      cid: 162
      inheritable: true
      inherited: true
    }
    "sp_default_document" => Pimcore\Model\Property {#1875
      #dao: null
      #name: "sp_default_document"
      #data: "56"
      #type: "document"
      #ctype: "document"
      #cpath: null
      #cid: 162
      #inheritable: true
      #inherited: true
      name: "sp_default_document"
      data: "56"
      type: "document"
      ctype: "document"
      cpath: null
      cid: 162
      inheritable: true
      inherited: true
    }
    "citation_start_doc" => Pimcore\Model\Property {#1874
      #dao: null
      #name: "citation_start_doc"
      #data: "160"
      #type: "document"
      #ctype: "document"
      #cpath: null
      #cid: 162
      #inheritable: true
      #inherited: true
      name: "citation_start_doc"
      data: "160"
      type: "document"
      ctype: "document"
      cpath: null
      cid: 162
      inheritable: true
      inherited: true
    }
    "navigation_name" => Pimcore\Model\Property {#1873
      #dao: null
      #name: "navigation_name"
      #data: "Recommendations for Data Repositories"
      #type: "text"
      #ctype: "document"
      #cpath: null
      #cid: 162
      #inheritable: false
      #inherited: false
      name: "navigation_name"
      data: "Recommendations for Data Repositories"
      type: "text"
      ctype: "document"
      cpath: null
      cid: 162
      inheritable: false
      inherited: false
    }
  ]
  #id: 162
  #creationDate: 1738759452
  #modificationDate: 1738759478
  #versionCount: 3
  #userOwner: 2
  #locked: null
  #userModification: 2
  #parentId: 160
  #parent: null
  #_fulldump: false
  #o_dirtyFields: null
  -activeDispatchingEvents: []
  #fullPathCache: "/Recommendations-for-Data-Repositories"
  #type: "page"
  #key: "Recommendations-for-Data-Repositories"
  #index: 2
  #published: true
  #children: []
  #hasChildren: []
  #siblings: []
  #hasSiblings: []
  #controller: "App\Controller\ContentController::dataCitationAction"
  #template: null
  #editables: [
    "contentblock" => Pimcore\Model\Document\Editable\Block {#3475
      #dao: null
      #config: [
        "limit" => 1000000
      ]
      #name: "contentblock"
      #realName: "contentblock"
      -parentBlockNames: []
      #documentId: 162
      #document: Pimcore\Model\Document\Page {#1894}
      #editmode: false
      #inherited: false
      #inDialogBox: null
      -editableDefinitionCollector: null
      #indices: [
        "1"
      ]
      #current: 0
      config: [
        "limit" => 1000000
      ]
      name: "contentblock"
      realName: "contentblock"
      documentId: 162
      document: Pimcore\Model\Document\Page {#1894}
      editmode: false
      inherited: false
      inDialogBox: null
      indices: [
        "1"
      ]
      current: 0
    }
    "contentblock:1.content" => Pimcore\Model\Document\Editable\Wysiwyg {#3474
      #dao: null
      #config: []
      #name: "contentblock:1.content"
      #realName: "content"
      -parentBlockNames: []
      #documentId: 162
      #document: Pimcore\Model\Document\Page {#1894}
      #editmode: false
      #inherited: false
      #inDialogBox: null
      -editableDefinitionCollector: null
      #text: """
        <h3>Recommendation 1 – Request data to be cited</h3>\n
        \n
        <p>Data repositories should request that data are cited whenever they are used or mentioned. Citing data is a sound scholarly practice. Enforcing the citation of data relies on contracts, licences, terms of use, or suggested best practices. Requesting data to be cited could also be stated in related documents included in the data package download folder, such as user terms and conditions, codebooks and data reports.&nbsp;</p>\n
        \n
        <h3><a name="_e5pmhf4701mt"></a>Recommendation 2 – Provide all six core data citation components</h3>\n
        \n
        <p>Data repositories should ensure that all data published are citable by providing at least the core components of a data citation, as listed above. Data repositories should check the quality of the metadata useful for the citation (e.g., explicit dataset title). Moreover, they are responsible for assigning a PID and providing the version (or publication date) for published datasets. Finally, for embargoed data, data repositories should provide a PID that allows data authors to cite the data in their research article. Reservation of a PID before the data are accessible should therefore be possible.</p>\n
        \n
        <h3><a name="_r5tv0kls4gs3"></a>Recommendation 3 – Provide data versioning and access information</h3>\n
        \n
        <p>Data citations should include the version of a dataset (or a publication date) to ensure reproducibility. Therefore, data users may need to access specific versions of datasets, and information about changes and versions of data should be available. This could be provided through specific PIDs for each version of the dataset and/or a changelog, or versioning information text for concept PIDs. If a dataset or version of a dataset is no longer available, the PID assigned in the data citation should still lead to metadata about the dataset on the repository websites (e.g., a tombstone page). Moreover, data repositories should ensure access to metadata about all published versions of a dataset.</p>\n
        \n
        <h3><a name="_wrpfy536syly"></a>Recommendation 4 – Provide data citation suggestions including all six core components</h3>\n
        \n
        <p>User-friendly access to citation information for each dataset should be provided on the repository website. The data repositories should provide a data citation suggestion for each dataset. This suggestion should always include at least the six core components, and be visually noticeable. Providing this citation in multiple formats (e.g., APA, Chicago, and Harvard) is considered a good practice.</p>\n
        \n
        <h3><a name="_4syaly57w3ip"></a>Recommendation 5 – Facilitate data citation for authors through export and download of metadata for reference management software</h3>\n
        \n
        <p>Data repositories should make it easy for users to automatically export and download data citation core components to reference management software. This will ensure that data can be cited in the same manner as other sources (such as journal articles, books, etc.) (Bornatici &amp; Fedrigo, 2023). It is recommended that data repositories use formats that are compatible with commonly used reference management software (e.g., Endnote, Mendeley and Zotero), such as the RIS format (Research Information System Document). These files should include at least the six core components needed to build a data citation.</p>\n
        \n
        <h3><a name="_p44ak2lcxv4v"></a>Recommendation 6 – Make citation information and other publication metadata accessible through generic structured metadata files</h3>\n
        \n
        <p>For the implementation of the FAIR principles, it is important to make sure that the six core components of a data citation are openly accessible together with other relevant information about the data publication as linked open metadata, thus providing a structured way of accessing a description of the data.</p>\n
        \n
        <p>At least one generic metadata container should be provided with the data publication in a standardised and machine-actionable linked data format, for example, JSON-LD or RDF/XML. The actual metadata standards implemented may vary, but should at the very least cover the basic needs of a data repository. An example of this is the DCAT standard (Albertoni et al., 2020). In specialised repositories, the schema used may depend on what relevant community standards are in use, for example, DDI-Lifecycle for the social sciences (DDI Alliance, 2024).</p>\n
        \n
        <p>In addition to metadata standards established specifically for describing data, it is also advisable to provide metadata files or tags that use a generic metadata schema such as Schema.org (Payne &amp; Verhey, 2022). This makes it more likely that infrastructures that are not specialised in research data will be able to reuse the six core components of a data citation and other information.</p>\n
        \n
        <p>The metadata contents should reflect community standards and needs, while also providing generic information such as details on access methods, licensing and conditions for data reuse. Ideally, it should provide all structured information included in the data repository entry itself.</p>\n
        \n
        <h3><a name="_172gzfirb165"></a>Recommendation 7 – Make data publications and relations to other entities machine-actionable through rich metadata and PIDs</h3>\n
        \n
        <p>In addition to the six core components of a data citation, the generic metadata containers should express relations between the data publication and other entities, using machine-actionable PIDs when possible. Examples of such PIDs and entities are ORCID for expressing relations to individuals, such as data authors and other contributors, ROR ID for expressing relations to organisations, such as research institutions, infrastructures or funders and DOI for expressing relations to publications and other digital objects. An example of expressing relations to publications would be including PIDs of publications citing the data as relations of a specific “cited by” type in the metadata. Such relations may also be enhanced over time by external metadata contributors.</p>\n
        \n
        <p>Data may be published with different hierarchical relations and varying granularity. Whenever possible, this should be expressed with PIDs and machine-actionable metadata. For example, a DOI could be provided pointing to the conceptual level of a data publication, with other DOIs pointing to specific versions or subsets of the data publication. In such cases, the latter type of PID would most often be the appropriate choice for inclusion in a data citation.</p>\n
        \n
        <h3><a name="_6uaupg3xw3"></a>Recommendation 8 –&nbsp; Raise awareness about data citation</h3>\n
        \n
        <p>Data repositories should inform data users on data citation best practices, for example through their general information materials or accompanying dataset documentation. Data repositories should also target data producers specifically and encourage them to cite their data and report the shared datasets alongside traditional research outputs. Similarly, data repositories should suggest to research institutions to include data collection and sharing, as well as data citations, in their research assessment process. In addition to creating specific documentation and teaching materials, seminars and presentations could be conducted to inform different stakeholders like researchers, students, institutions, funders, and journals on best practices. Data repositories could thus emphasise the benefits of correct data citation, such as aligning with open data principles and fostering better research practices. Recognising data authors for sharing data gives them more incentives to share their data, which ultimately increases repository content.</p>\n
        """
      config: []
      name: "contentblock:1.content"
      realName: "content"
      documentId: 162
      document: Pimcore\Model\Document\Page {#1894}
      editmode: false
      inherited: false
      inDialogBox: null
      text: """
        <h3>Recommendation 1 – Request data to be cited</h3>\n
        \n
        <p>Data repositories should request that data are cited whenever they are used or mentioned. Citing data is a sound scholarly practice. Enforcing the citation of data relies on contracts, licences, terms of use, or suggested best practices. Requesting data to be cited could also be stated in related documents included in the data package download folder, such as user terms and conditions, codebooks and data reports.&nbsp;</p>\n
        \n
        <h3><a name="_e5pmhf4701mt"></a>Recommendation 2 – Provide all six core data citation components</h3>\n
        \n
        <p>Data repositories should ensure that all data published are citable by providing at least the core components of a data citation, as listed above. Data repositories should check the quality of the metadata useful for the citation (e.g., explicit dataset title). Moreover, they are responsible for assigning a PID and providing the version (or publication date) for published datasets. Finally, for embargoed data, data repositories should provide a PID that allows data authors to cite the data in their research article. Reservation of a PID before the data are accessible should therefore be possible.</p>\n
        \n
        <h3><a name="_r5tv0kls4gs3"></a>Recommendation 3 – Provide data versioning and access information</h3>\n
        \n
        <p>Data citations should include the version of a dataset (or a publication date) to ensure reproducibility. Therefore, data users may need to access specific versions of datasets, and information about changes and versions of data should be available. This could be provided through specific PIDs for each version of the dataset and/or a changelog, or versioning information text for concept PIDs. If a dataset or version of a dataset is no longer available, the PID assigned in the data citation should still lead to metadata about the dataset on the repository websites (e.g., a tombstone page). Moreover, data repositories should ensure access to metadata about all published versions of a dataset.</p>\n
        \n
        <h3><a name="_wrpfy536syly"></a>Recommendation 4 – Provide data citation suggestions including all six core components</h3>\n
        \n
        <p>User-friendly access to citation information for each dataset should be provided on the repository website. The data repositories should provide a data citation suggestion for each dataset. This suggestion should always include at least the six core components, and be visually noticeable. Providing this citation in multiple formats (e.g., APA, Chicago, and Harvard) is considered a good practice.</p>\n
        \n
        <h3><a name="_4syaly57w3ip"></a>Recommendation 5 – Facilitate data citation for authors through export and download of metadata for reference management software</h3>\n
        \n
        <p>Data repositories should make it easy for users to automatically export and download data citation core components to reference management software. This will ensure that data can be cited in the same manner as other sources (such as journal articles, books, etc.) (Bornatici &amp; Fedrigo, 2023). It is recommended that data repositories use formats that are compatible with commonly used reference management software (e.g., Endnote, Mendeley and Zotero), such as the RIS format (Research Information System Document). These files should include at least the six core components needed to build a data citation.</p>\n
        \n
        <h3><a name="_p44ak2lcxv4v"></a>Recommendation 6 – Make citation information and other publication metadata accessible through generic structured metadata files</h3>\n
        \n
        <p>For the implementation of the FAIR principles, it is important to make sure that the six core components of a data citation are openly accessible together with other relevant information about the data publication as linked open metadata, thus providing a structured way of accessing a description of the data.</p>\n
        \n
        <p>At least one generic metadata container should be provided with the data publication in a standardised and machine-actionable linked data format, for example, JSON-LD or RDF/XML. The actual metadata standards implemented may vary, but should at the very least cover the basic needs of a data repository. An example of this is the DCAT standard (Albertoni et al., 2020). In specialised repositories, the schema used may depend on what relevant community standards are in use, for example, DDI-Lifecycle for the social sciences (DDI Alliance, 2024).</p>\n
        \n
        <p>In addition to metadata standards established specifically for describing data, it is also advisable to provide metadata files or tags that use a generic metadata schema such as Schema.org (Payne &amp; Verhey, 2022). This makes it more likely that infrastructures that are not specialised in research data will be able to reuse the six core components of a data citation and other information.</p>\n
        \n
        <p>The metadata contents should reflect community standards and needs, while also providing generic information such as details on access methods, licensing and conditions for data reuse. Ideally, it should provide all structured information included in the data repository entry itself.</p>\n
        \n
        <h3><a name="_172gzfirb165"></a>Recommendation 7 – Make data publications and relations to other entities machine-actionable through rich metadata and PIDs</h3>\n
        \n
        <p>In addition to the six core components of a data citation, the generic metadata containers should express relations between the data publication and other entities, using machine-actionable PIDs when possible. Examples of such PIDs and entities are ORCID for expressing relations to individuals, such as data authors and other contributors, ROR ID for expressing relations to organisations, such as research institutions, infrastructures or funders and DOI for expressing relations to publications and other digital objects. An example of expressing relations to publications would be including PIDs of publications citing the data as relations of a specific “cited by” type in the metadata. Such relations may also be enhanced over time by external metadata contributors.</p>\n
        \n
        <p>Data may be published with different hierarchical relations and varying granularity. Whenever possible, this should be expressed with PIDs and machine-actionable metadata. For example, a DOI could be provided pointing to the conceptual level of a data publication, with other DOIs pointing to specific versions or subsets of the data publication. In such cases, the latter type of PID would most often be the appropriate choice for inclusion in a data citation.</p>\n
        \n
        <h3><a name="_6uaupg3xw3"></a>Recommendation 8 –&nbsp; Raise awareness about data citation</h3>\n
        \n
        <p>Data repositories should inform data users on data citation best practices, for example through their general information materials or accompanying dataset documentation. Data repositories should also target data producers specifically and encourage them to cite their data and report the shared datasets alongside traditional research outputs. Similarly, data repositories should suggest to research institutions to include data collection and sharing, as well as data citations, in their research assessment process. In addition to creating specific documentation and teaching materials, seminars and presentations could be conducted to inform different stakeholders like researchers, students, institutions, funders, and journals on best practices. Data repositories could thus emphasise the benefits of correct data citation, such as aligning with open data principles and fostering better research practices. Recognising data authors for sharing data gives them more incentives to share their data, which ultimately increases repository content.</p>\n
        """
    }
    "headline" => Pimcore\Model\Document\Editable\Input {#3480
      #dao: null
      #config: [
        "placeholder" => "Headline"
        "width" => 600
      ]
      #name: "headline"
      #realName: "headline"
      -parentBlockNames: []
      #documentId: 162
      #document: Pimcore\Model\Document\Page {#1894}
      #editmode: false
      #inherited: false
      #inDialogBox: null
      -editableDefinitionCollector: null
      #text: "Recommendations for Data Repositories"
      config: [
        "placeholder" => "Headline"
        "width" => 600
      ]
      name: "headline"
      realName: "headline"
      documentId: 162
      document: Pimcore\Model\Document\Page {#1894}
      editmode: false
      inherited: false
      inDialogBox: null
      text: "Recommendations for Data Repositories"
    }
    "main_content" => Pimcore\Model\Document\Editable\Areablock {#3476
      #dao: null
      #config: [
        "allowed" => [
          "video"
          "wysiwyg"
          "resource-collection"
          "map"
          "staff"
          "text-accordion"
          "organigramme"
        ]
        "sorting" => [
          "wysiwyg"
          "text-accordion"
          "video"
          "resource-collection"
          "map"
          "staff"
          "organigramme"
        ]
        "types" => [
          [
            "name" => "Rich Text"
            "description" => ""
            "type" => "wysiwyg"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/wysiwyg.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 0
          ]
          [
            "name" => "Text Accordion"
            "description" => ""
            "type" => "text-accordion"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/database.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 1
          ]
          [
            "name" => "Video"
            "description" => ""
            "type" => "video"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/video_file.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 2
          ]
          [
            "name" => "Resource Collection"
            "description" => ""
            "type" => "resource-collection"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/fieldset.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 3
          ]
          [
            "name" => "Member map"
            "description" => ""
            "type" => "map"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/marker.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 4
          ]
          [
            "name" => "Staff cards"
            "description" => ""
            "type" => "staff"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/address_book.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 5
          ]
          [
            "name" => "Organigramme"
            "description" => ""
            "type" => "organigramme"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/parallel_tasks.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 6
          ]
        ]
        "limit" => 1000000
        "blockStateStack" => "[{"blocks":[],"indexes":[]}]"
      ]
      #name: "main_content"
      #realName: "main_content"
      -parentBlockNames: []
      #documentId: 162
      #document: Pimcore\Model\Document\Page {#1894}
      #editmode: false
      #inherited: false
      #inDialogBox: null
      -editableDefinitionCollector: null
      #indices: []
      #current: 0
      #currentIndex: null
      #blockStarted: null
      #brickTypeUsageCounter: []
      config: [
        "allowed" => [
          "video"
          "wysiwyg"
          "resource-collection"
          "map"
          "staff"
          "text-accordion"
          "organigramme"
        ]
        "sorting" => [
          "wysiwyg"
          "text-accordion"
          "video"
          "resource-collection"
          "map"
          "staff"
          "organigramme"
        ]
        "types" => [
          [
            "name" => "Rich Text"
            "description" => ""
            "type" => "wysiwyg"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/wysiwyg.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 0
          ]
          [
            "name" => "Text Accordion"
            "description" => ""
            "type" => "text-accordion"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/database.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 1
          ]
          [
            "name" => "Video"
            "description" => ""
            "type" => "video"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/video_file.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 2
          ]
          [
            "name" => "Resource Collection"
            "description" => ""
            "type" => "resource-collection"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/fieldset.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 3
          ]
          [
            "name" => "Member map"
            "description" => ""
            "type" => "map"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/marker.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 4
          ]
          [
            "name" => "Staff cards"
            "description" => ""
            "type" => "staff"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/address_book.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 5
          ]
          [
            "name" => "Organigramme"
            "description" => ""
            "type" => "organigramme"
            "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/parallel_tasks.svg"
            "previewHtml" => null
            "limit" => null
            "needsReload" => false
            "hasDialogBoxConfiguration" => false
            "sortIndex" => 6
          ]
        ]
        "limit" => 1000000
        "blockStateStack" => "[{"blocks":[],"indexes":[]}]"
      ]
      name: "main_content"
      realName: "main_content"
      documentId: 162
      document: Pimcore\Model\Document\Page {#1894}
      editmode: false
      inherited: false
      inDialogBox: null
      indices: []
      current: 0
      currentIndex: null
      blockStarted: null
      brickTypeUsageCounter: []
    }
  ]
  #versions: null
  #contentMasterDocumentId: null
  #supportsContentMaster: true
  #missingRequiredEditable: null
  #staticGeneratorEnabled: null
  #staticGeneratorLifetime: null
  #inheritedEditables: []
  #scheduledTasks: null
  -useTargetGroup: null
  #title: "Recommendations for Data Repositories"
  #description: ""
  #metaData: []
  #prettyUrl: null
  #targetGroupIds: ""
  +"____pimcore_cache_item__": "document_162"
  dependencies: null
  __dataVersionTimestamp: 1738759478
  path: "/Data-Citation/"
  properties: [
    "blog_default_document" => Pimcore\Model\Property {#1891}
    "event_default_document" => Pimcore\Model\Property {#1885}
    "fallback_newsimg" => Pimcore\Model\Property {#1884}
    "language" => Pimcore\Model\Property {#1879}
    "navigation_root" => Pimcore\Model\Property {#1880}
    "news_default_document" => Pimcore\Model\Property {#1881}
    "project_default_document" => Pimcore\Model\Property {#1882}
    "rdresource_default_document" => Pimcore\Model\Property {#1878}
    "resource_default_document" => Pimcore\Model\Property {#1876}
    "sp_default_document" => Pimcore\Model\Property {#1875}
    "citation_start_doc" => Pimcore\Model\Property {#1874}
    "navigation_name" => Pimcore\Model\Property {#1873}
  ]
  id: 162
  creationDate: 1738759452
  modificationDate: 1738759478
  versionCount: 3
  userOwner: 2
  locked: null
  userModification: 2
  parentId: 160
  parent: null
  _fulldump: false
  o_dirtyFields: null
  fullPathCache: "/Recommendations-for-Data-Repositories"
  type: "page"
  key: "Recommendations-for-Data-Repositories"
  index: 2
  published: true
  children: []
  hasChildren: []
  siblings: []
  hasSiblings: []
  controller: "App\Controller\ContentController::dataCitationAction"
  template: null
  editables: [
    "contentblock" => Pimcore\Model\Document\Editable\Block {#3475}
    "contentblock:1.content" => Pimcore\Model\Document\Editable\Wysiwyg {#3474}
    "headline" => Pimcore\Model\Document\Editable\Input {#3480}
    "main_content" => Pimcore\Model\Document\Editable\Areablock {#3476}
  ]
  versions: null
  contentMasterDocumentId: null
  supportsContentMaster: true
  missingRequiredEditable: null
  staticGeneratorEnabled: null
  staticGeneratorLifetime: null
  inheritedEditables: []
  scheduledTasks: null
  title: "Recommendations for Data Repositories"
  description: ""
  metaData: []
  prettyUrl: null
  targetGroupIds: ""
}
routeDocument 
Pimcore\Routing\DocumentRoute {#1877
  -path: "/Recommendations-for-Data-Repositories"
  -host: ""
  -schemes: []
  -methods: []
  -defaults: [
    "_locale" => null
    "_controller" => "App\Controller\ContentController::dataCitationAction"
  ]
  -requirements: []
  -options: [
    "compiler_class" => "Symfony\Component\Routing\RouteCompiler"
    "utf8" => true
  ]
  -condition: ""
  -compiled: Symfony\Component\Routing\CompiledRoute {#1867 …}
  #document: Pimcore\Model\Document\Page {#1894
    #dao: Pimcore\Model\Document\Page\Dao {#3472 …}
    #dependencies: null
    #__dataVersionTimestamp: 1738759478
    #path: "/Data-Citation/"
    #properties: [
      "blog_default_document" => Pimcore\Model\Property {#1891
        #dao: null
        #name: "blog_default_document"
        #data: "51"
        #type: "document"
        #ctype: "document"
        #cpath: null
        #cid: 162
        #inheritable: true
        #inherited: true
        name: "blog_default_document"
        data: "51"
        type: "document"
        ctype: "document"
        cpath: null
        cid: 162
        inheritable: true
        inherited: true
      }
      "event_default_document" => Pimcore\Model\Property {#1885
        #dao: null
        #name: "event_default_document"
        #data: "44"
        #type: "document"
        #ctype: "document"
        #cpath: null
        #cid: 162
        #inheritable: true
        #inherited: true
        name: "event_default_document"
        data: "44"
        type: "document"
        ctype: "document"
        cpath: null
        cid: 162
        inheritable: true
        inherited: true
      }
      "fallback_newsimg" => Pimcore\Model\Property {#1884
        #dao: null
        #name: "fallback_newsimg"
        #data: "488"
        #type: "asset"
        #ctype: "document"
        #cpath: null
        #cid: 162
        #inheritable: true
        #inherited: true
        name: "fallback_newsimg"
        data: "488"
        type: "asset"
        ctype: "document"
        cpath: null
        cid: 162
        inheritable: true
        inherited: true
      }
      "language" => Pimcore\Model\Property {#1879
        #dao: null
        #name: "language"
        #data: null
        #type: "text"
        #ctype: "document"
        #cpath: null
        #cid: 162
        #inheritable: true
        #inherited: true
        name: "language"
        data: null
        type: "text"
        ctype: "document"
        cpath: null
        cid: 162
        inheritable: true
        inherited: true
      }
      "navigation_root" => Pimcore\Model\Property {#1880
        #dao: null
        #name: "navigation_root"
        #data: "1"
        #type: "document"
        #ctype: "document"
        #cpath: null
        #cid: 162
        #inheritable: true
        #inherited: true
        name: "navigation_root"
        data: "1"
        type: "document"
        ctype: "document"
        cpath: null
        cid: 162
        inheritable: true
        inherited: true
      }
      "news_default_document" => Pimcore\Model\Property {#1881
        #dao: null
        #name: "news_default_document"
        #data: "43"
        #type: "document"
        #ctype: "document"
        #cpath: null
        #cid: 162
        #inheritable: true
        #inherited: true
        name: "news_default_document"
        data: "43"
        type: "document"
        ctype: "document"
        cpath: null
        cid: 162
        inheritable: true
        inherited: true
      }
      "project_default_document" => Pimcore\Model\Property {#1882
        #dao: null
        #name: "project_default_document"
        #data: "25"
        #type: "document"
        #ctype: "document"
        #cpath: null
        #cid: 162
        #inheritable: true
        #inherited: true
        name: "project_default_document"
        data: "25"
        type: "document"
        ctype: "document"
        cpath: null
        cid: 162
        inheritable: true
        inherited: true
      }
      "rdresource_default_document" => Pimcore\Model\Property {#1878
        #dao: null
        #name: "rdresource_default_document"
        #data: "159"
        #type: "document"
        #ctype: "document"
        #cpath: null
        #cid: 162
        #inheritable: true
        #inherited: true
        name: "rdresource_default_document"
        data: "159"
        type: "document"
        ctype: "document"
        cpath: null
        cid: 162
        inheritable: true
        inherited: true
      }
      "resource_default_document" => Pimcore\Model\Property {#1876
        #dao: null
        #name: "resource_default_document"
        #data: "6"
        #type: "document"
        #ctype: "document"
        #cpath: null
        #cid: 162
        #inheritable: true
        #inherited: true
        name: "resource_default_document"
        data: "6"
        type: "document"
        ctype: "document"
        cpath: null
        cid: 162
        inheritable: true
        inherited: true
      }
      "sp_default_document" => Pimcore\Model\Property {#1875
        #dao: null
        #name: "sp_default_document"
        #data: "56"
        #type: "document"
        #ctype: "document"
        #cpath: null
        #cid: 162
        #inheritable: true
        #inherited: true
        name: "sp_default_document"
        data: "56"
        type: "document"
        ctype: "document"
        cpath: null
        cid: 162
        inheritable: true
        inherited: true
      }
      "citation_start_doc" => Pimcore\Model\Property {#1874
        #dao: null
        #name: "citation_start_doc"
        #data: "160"
        #type: "document"
        #ctype: "document"
        #cpath: null
        #cid: 162
        #inheritable: true
        #inherited: true
        name: "citation_start_doc"
        data: "160"
        type: "document"
        ctype: "document"
        cpath: null
        cid: 162
        inheritable: true
        inherited: true
      }
      "navigation_name" => Pimcore\Model\Property {#1873
        #dao: null
        #name: "navigation_name"
        #data: "Recommendations for Data Repositories"
        #type: "text"
        #ctype: "document"
        #cpath: null
        #cid: 162
        #inheritable: false
        #inherited: false
        name: "navigation_name"
        data: "Recommendations for Data Repositories"
        type: "text"
        ctype: "document"
        cpath: null
        cid: 162
        inheritable: false
        inherited: false
      }
    ]
    #id: 162
    #creationDate: 1738759452
    #modificationDate: 1738759478
    #versionCount: 3
    #userOwner: 2
    #locked: null
    #userModification: 2
    #parentId: 160
    #parent: null
    #_fulldump: false
    #o_dirtyFields: null
    -activeDispatchingEvents: []
    #fullPathCache: "/Recommendations-for-Data-Repositories"
    #type: "page"
    #key: "Recommendations-for-Data-Repositories"
    #index: 2
    #published: true
    #children: []
    #hasChildren: []
    #siblings: []
    #hasSiblings: []
    #controller: "App\Controller\ContentController::dataCitationAction"
    #template: null
    #editables: [
      "contentblock" => Pimcore\Model\Document\Editable\Block {#3475
        #dao: null
        #config: [
          "limit" => 1000000
        ]
        #name: "contentblock"
        #realName: "contentblock"
        -parentBlockNames: []
        #documentId: 162
        #document: Pimcore\Model\Document\Page {#1894}
        #editmode: false
        #inherited: false
        #inDialogBox: null
        -editableDefinitionCollector: null
        #indices: [
          "1"
        ]
        #current: 0
        config: [
          "limit" => 1000000
        ]
        name: "contentblock"
        realName: "contentblock"
        documentId: 162
        document: Pimcore\Model\Document\Page {#1894}
        editmode: false
        inherited: false
        inDialogBox: null
        indices: [
          "1"
        ]
        current: 0
      }
      "contentblock:1.content" => Pimcore\Model\Document\Editable\Wysiwyg {#3474
        #dao: null
        #config: []
        #name: "contentblock:1.content"
        #realName: "content"
        -parentBlockNames: []
        #documentId: 162
        #document: Pimcore\Model\Document\Page {#1894}
        #editmode: false
        #inherited: false
        #inDialogBox: null
        -editableDefinitionCollector: null
        #text: """
          <h3>Recommendation 1 – Request data to be cited</h3>\n
          \n
          <p>Data repositories should request that data are cited whenever they are used or mentioned. Citing data is a sound scholarly practice. Enforcing the citation of data relies on contracts, licences, terms of use, or suggested best practices. Requesting data to be cited could also be stated in related documents included in the data package download folder, such as user terms and conditions, codebooks and data reports.&nbsp;</p>\n
          \n
          <h3><a name="_e5pmhf4701mt"></a>Recommendation 2 – Provide all six core data citation components</h3>\n
          \n
          <p>Data repositories should ensure that all data published are citable by providing at least the core components of a data citation, as listed above. Data repositories should check the quality of the metadata useful for the citation (e.g., explicit dataset title). Moreover, they are responsible for assigning a PID and providing the version (or publication date) for published datasets. Finally, for embargoed data, data repositories should provide a PID that allows data authors to cite the data in their research article. Reservation of a PID before the data are accessible should therefore be possible.</p>\n
          \n
          <h3><a name="_r5tv0kls4gs3"></a>Recommendation 3 – Provide data versioning and access information</h3>\n
          \n
          <p>Data citations should include the version of a dataset (or a publication date) to ensure reproducibility. Therefore, data users may need to access specific versions of datasets, and information about changes and versions of data should be available. This could be provided through specific PIDs for each version of the dataset and/or a changelog, or versioning information text for concept PIDs. If a dataset or version of a dataset is no longer available, the PID assigned in the data citation should still lead to metadata about the dataset on the repository websites (e.g., a tombstone page). Moreover, data repositories should ensure access to metadata about all published versions of a dataset.</p>\n
          \n
          <h3><a name="_wrpfy536syly"></a>Recommendation 4 – Provide data citation suggestions including all six core components</h3>\n
          \n
          <p>User-friendly access to citation information for each dataset should be provided on the repository website. The data repositories should provide a data citation suggestion for each dataset. This suggestion should always include at least the six core components, and be visually noticeable. Providing this citation in multiple formats (e.g., APA, Chicago, and Harvard) is considered a good practice.</p>\n
          \n
          <h3><a name="_4syaly57w3ip"></a>Recommendation 5 – Facilitate data citation for authors through export and download of metadata for reference management software</h3>\n
          \n
          <p>Data repositories should make it easy for users to automatically export and download data citation core components to reference management software. This will ensure that data can be cited in the same manner as other sources (such as journal articles, books, etc.) (Bornatici &amp; Fedrigo, 2023). It is recommended that data repositories use formats that are compatible with commonly used reference management software (e.g., Endnote, Mendeley and Zotero), such as the RIS format (Research Information System Document). These files should include at least the six core components needed to build a data citation.</p>\n
          \n
          <h3><a name="_p44ak2lcxv4v"></a>Recommendation 6 – Make citation information and other publication metadata accessible through generic structured metadata files</h3>\n
          \n
          <p>For the implementation of the FAIR principles, it is important to make sure that the six core components of a data citation are openly accessible together with other relevant information about the data publication as linked open metadata, thus providing a structured way of accessing a description of the data.</p>\n
          \n
          <p>At least one generic metadata container should be provided with the data publication in a standardised and machine-actionable linked data format, for example, JSON-LD or RDF/XML. The actual metadata standards implemented may vary, but should at the very least cover the basic needs of a data repository. An example of this is the DCAT standard (Albertoni et al., 2020). In specialised repositories, the schema used may depend on what relevant community standards are in use, for example, DDI-Lifecycle for the social sciences (DDI Alliance, 2024).</p>\n
          \n
          <p>In addition to metadata standards established specifically for describing data, it is also advisable to provide metadata files or tags that use a generic metadata schema such as Schema.org (Payne &amp; Verhey, 2022). This makes it more likely that infrastructures that are not specialised in research data will be able to reuse the six core components of a data citation and other information.</p>\n
          \n
          <p>The metadata contents should reflect community standards and needs, while also providing generic information such as details on access methods, licensing and conditions for data reuse. Ideally, it should provide all structured information included in the data repository entry itself.</p>\n
          \n
          <h3><a name="_172gzfirb165"></a>Recommendation 7 – Make data publications and relations to other entities machine-actionable through rich metadata and PIDs</h3>\n
          \n
          <p>In addition to the six core components of a data citation, the generic metadata containers should express relations between the data publication and other entities, using machine-actionable PIDs when possible. Examples of such PIDs and entities are ORCID for expressing relations to individuals, such as data authors and other contributors, ROR ID for expressing relations to organisations, such as research institutions, infrastructures or funders and DOI for expressing relations to publications and other digital objects. An example of expressing relations to publications would be including PIDs of publications citing the data as relations of a specific “cited by” type in the metadata. Such relations may also be enhanced over time by external metadata contributors.</p>\n
          \n
          <p>Data may be published with different hierarchical relations and varying granularity. Whenever possible, this should be expressed with PIDs and machine-actionable metadata. For example, a DOI could be provided pointing to the conceptual level of a data publication, with other DOIs pointing to specific versions or subsets of the data publication. In such cases, the latter type of PID would most often be the appropriate choice for inclusion in a data citation.</p>\n
          \n
          <h3><a name="_6uaupg3xw3"></a>Recommendation 8 –&nbsp; Raise awareness about data citation</h3>\n
          \n
          <p>Data repositories should inform data users on data citation best practices, for example through their general information materials or accompanying dataset documentation. Data repositories should also target data producers specifically and encourage them to cite their data and report the shared datasets alongside traditional research outputs. Similarly, data repositories should suggest to research institutions to include data collection and sharing, as well as data citations, in their research assessment process. In addition to creating specific documentation and teaching materials, seminars and presentations could be conducted to inform different stakeholders like researchers, students, institutions, funders, and journals on best practices. Data repositories could thus emphasise the benefits of correct data citation, such as aligning with open data principles and fostering better research practices. Recognising data authors for sharing data gives them more incentives to share their data, which ultimately increases repository content.</p>\n
          """
        config: []
        name: "contentblock:1.content"
        realName: "content"
        documentId: 162
        document: Pimcore\Model\Document\Page {#1894}
        editmode: false
        inherited: false
        inDialogBox: null
        text: """
          <h3>Recommendation 1 – Request data to be cited</h3>\n
          \n
          <p>Data repositories should request that data are cited whenever they are used or mentioned. Citing data is a sound scholarly practice. Enforcing the citation of data relies on contracts, licences, terms of use, or suggested best practices. Requesting data to be cited could also be stated in related documents included in the data package download folder, such as user terms and conditions, codebooks and data reports.&nbsp;</p>\n
          \n
          <h3><a name="_e5pmhf4701mt"></a>Recommendation 2 – Provide all six core data citation components</h3>\n
          \n
          <p>Data repositories should ensure that all data published are citable by providing at least the core components of a data citation, as listed above. Data repositories should check the quality of the metadata useful for the citation (e.g., explicit dataset title). Moreover, they are responsible for assigning a PID and providing the version (or publication date) for published datasets. Finally, for embargoed data, data repositories should provide a PID that allows data authors to cite the data in their research article. Reservation of a PID before the data are accessible should therefore be possible.</p>\n
          \n
          <h3><a name="_r5tv0kls4gs3"></a>Recommendation 3 – Provide data versioning and access information</h3>\n
          \n
          <p>Data citations should include the version of a dataset (or a publication date) to ensure reproducibility. Therefore, data users may need to access specific versions of datasets, and information about changes and versions of data should be available. This could be provided through specific PIDs for each version of the dataset and/or a changelog, or versioning information text for concept PIDs. If a dataset or version of a dataset is no longer available, the PID assigned in the data citation should still lead to metadata about the dataset on the repository websites (e.g., a tombstone page). Moreover, data repositories should ensure access to metadata about all published versions of a dataset.</p>\n
          \n
          <h3><a name="_wrpfy536syly"></a>Recommendation 4 – Provide data citation suggestions including all six core components</h3>\n
          \n
          <p>User-friendly access to citation information for each dataset should be provided on the repository website. The data repositories should provide a data citation suggestion for each dataset. This suggestion should always include at least the six core components, and be visually noticeable. Providing this citation in multiple formats (e.g., APA, Chicago, and Harvard) is considered a good practice.</p>\n
          \n
          <h3><a name="_4syaly57w3ip"></a>Recommendation 5 – Facilitate data citation for authors through export and download of metadata for reference management software</h3>\n
          \n
          <p>Data repositories should make it easy for users to automatically export and download data citation core components to reference management software. This will ensure that data can be cited in the same manner as other sources (such as journal articles, books, etc.) (Bornatici &amp; Fedrigo, 2023). It is recommended that data repositories use formats that are compatible with commonly used reference management software (e.g., Endnote, Mendeley and Zotero), such as the RIS format (Research Information System Document). These files should include at least the six core components needed to build a data citation.</p>\n
          \n
          <h3><a name="_p44ak2lcxv4v"></a>Recommendation 6 – Make citation information and other publication metadata accessible through generic structured metadata files</h3>\n
          \n
          <p>For the implementation of the FAIR principles, it is important to make sure that the six core components of a data citation are openly accessible together with other relevant information about the data publication as linked open metadata, thus providing a structured way of accessing a description of the data.</p>\n
          \n
          <p>At least one generic metadata container should be provided with the data publication in a standardised and machine-actionable linked data format, for example, JSON-LD or RDF/XML. The actual metadata standards implemented may vary, but should at the very least cover the basic needs of a data repository. An example of this is the DCAT standard (Albertoni et al., 2020). In specialised repositories, the schema used may depend on what relevant community standards are in use, for example, DDI-Lifecycle for the social sciences (DDI Alliance, 2024).</p>\n
          \n
          <p>In addition to metadata standards established specifically for describing data, it is also advisable to provide metadata files or tags that use a generic metadata schema such as Schema.org (Payne &amp; Verhey, 2022). This makes it more likely that infrastructures that are not specialised in research data will be able to reuse the six core components of a data citation and other information.</p>\n
          \n
          <p>The metadata contents should reflect community standards and needs, while also providing generic information such as details on access methods, licensing and conditions for data reuse. Ideally, it should provide all structured information included in the data repository entry itself.</p>\n
          \n
          <h3><a name="_172gzfirb165"></a>Recommendation 7 – Make data publications and relations to other entities machine-actionable through rich metadata and PIDs</h3>\n
          \n
          <p>In addition to the six core components of a data citation, the generic metadata containers should express relations between the data publication and other entities, using machine-actionable PIDs when possible. Examples of such PIDs and entities are ORCID for expressing relations to individuals, such as data authors and other contributors, ROR ID for expressing relations to organisations, such as research institutions, infrastructures or funders and DOI for expressing relations to publications and other digital objects. An example of expressing relations to publications would be including PIDs of publications citing the data as relations of a specific “cited by” type in the metadata. Such relations may also be enhanced over time by external metadata contributors.</p>\n
          \n
          <p>Data may be published with different hierarchical relations and varying granularity. Whenever possible, this should be expressed with PIDs and machine-actionable metadata. For example, a DOI could be provided pointing to the conceptual level of a data publication, with other DOIs pointing to specific versions or subsets of the data publication. In such cases, the latter type of PID would most often be the appropriate choice for inclusion in a data citation.</p>\n
          \n
          <h3><a name="_6uaupg3xw3"></a>Recommendation 8 –&nbsp; Raise awareness about data citation</h3>\n
          \n
          <p>Data repositories should inform data users on data citation best practices, for example through their general information materials or accompanying dataset documentation. Data repositories should also target data producers specifically and encourage them to cite their data and report the shared datasets alongside traditional research outputs. Similarly, data repositories should suggest to research institutions to include data collection and sharing, as well as data citations, in their research assessment process. In addition to creating specific documentation and teaching materials, seminars and presentations could be conducted to inform different stakeholders like researchers, students, institutions, funders, and journals on best practices. Data repositories could thus emphasise the benefits of correct data citation, such as aligning with open data principles and fostering better research practices. Recognising data authors for sharing data gives them more incentives to share their data, which ultimately increases repository content.</p>\n
          """
      }
      "headline" => Pimcore\Model\Document\Editable\Input {#3480
        #dao: null
        #config: [
          "placeholder" => "Headline"
          "width" => 600
        ]
        #name: "headline"
        #realName: "headline"
        -parentBlockNames: []
        #documentId: 162
        #document: Pimcore\Model\Document\Page {#1894}
        #editmode: false
        #inherited: false
        #inDialogBox: null
        -editableDefinitionCollector: null
        #text: "Recommendations for Data Repositories"
        config: [
          "placeholder" => "Headline"
          "width" => 600
        ]
        name: "headline"
        realName: "headline"
        documentId: 162
        document: Pimcore\Model\Document\Page {#1894}
        editmode: false
        inherited: false
        inDialogBox: null
        text: "Recommendations for Data Repositories"
      }
      "main_content" => Pimcore\Model\Document\Editable\Areablock {#3476
        #dao: null
        #config: [
          "allowed" => [
            "video"
            "wysiwyg"
            "resource-collection"
            "map"
            "staff"
            "text-accordion"
            "organigramme"
          ]
          "sorting" => [
            "wysiwyg"
            "text-accordion"
            "video"
            "resource-collection"
            "map"
            "staff"
            "organigramme"
          ]
          "types" => [
            [
              "name" => "Rich Text"
              "description" => ""
              "type" => "wysiwyg"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/wysiwyg.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 0
            ]
            [
              "name" => "Text Accordion"
              "description" => ""
              "type" => "text-accordion"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/database.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 1
            ]
            [
              "name" => "Video"
              "description" => ""
              "type" => "video"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/video_file.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 2
            ]
            [
              "name" => "Resource Collection"
              "description" => ""
              "type" => "resource-collection"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/fieldset.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 3
            ]
            [
              "name" => "Member map"
              "description" => ""
              "type" => "map"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/marker.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 4
            ]
            [
              "name" => "Staff cards"
              "description" => ""
              "type" => "staff"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/address_book.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 5
            ]
            [
              "name" => "Organigramme"
              "description" => ""
              "type" => "organigramme"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/parallel_tasks.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 6
            ]
          ]
          "limit" => 1000000
          "blockStateStack" => "[{"blocks":[],"indexes":[]}]"
        ]
        #name: "main_content"
        #realName: "main_content"
        -parentBlockNames: []
        #documentId: 162
        #document: Pimcore\Model\Document\Page {#1894}
        #editmode: false
        #inherited: false
        #inDialogBox: null
        -editableDefinitionCollector: null
        #indices: []
        #current: 0
        #currentIndex: null
        #blockStarted: null
        #brickTypeUsageCounter: []
        config: [
          "allowed" => [
            "video"
            "wysiwyg"
            "resource-collection"
            "map"
            "staff"
            "text-accordion"
            "organigramme"
          ]
          "sorting" => [
            "wysiwyg"
            "text-accordion"
            "video"
            "resource-collection"
            "map"
            "staff"
            "organigramme"
          ]
          "types" => [
            [
              "name" => "Rich Text"
              "description" => ""
              "type" => "wysiwyg"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/wysiwyg.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 0
            ]
            [
              "name" => "Text Accordion"
              "description" => ""
              "type" => "text-accordion"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/database.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 1
            ]
            [
              "name" => "Video"
              "description" => ""
              "type" => "video"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/video_file.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 2
            ]
            [
              "name" => "Resource Collection"
              "description" => ""
              "type" => "resource-collection"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/fieldset.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 3
            ]
            [
              "name" => "Member map"
              "description" => ""
              "type" => "map"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/marker.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 4
            ]
            [
              "name" => "Staff cards"
              "description" => ""
              "type" => "staff"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/address_book.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 5
            ]
            [
              "name" => "Organigramme"
              "description" => ""
              "type" => "organigramme"
              "icon" => "/bundles/pimcoreadmin/img/flat-color-icons/parallel_tasks.svg"
              "previewHtml" => null
              "limit" => null
              "needsReload" => false
              "hasDialogBoxConfiguration" => false
              "sortIndex" => 6
            ]
          ]
          "limit" => 1000000
          "blockStateStack" => "[{"blocks":[],"indexes":[]}]"
        ]
        name: "main_content"
        realName: "main_content"
        documentId: 162
        document: Pimcore\Model\Document\Page {#1894}
        editmode: false
        inherited: false
        inDialogBox: null
        indices: []
        current: 0
        currentIndex: null
        blockStarted: null
        brickTypeUsageCounter: []
      }
    ]
    #versions: null
    #contentMasterDocumentId: null
    #supportsContentMaster: true
    #missingRequiredEditable: null
    #staticGeneratorEnabled: null
    #staticGeneratorLifetime: null
    #inheritedEditables: []
    #scheduledTasks: null
    -useTargetGroup: null
    #title: "Recommendations for Data Repositories"
    #description: ""
    #metaData: []
    #prettyUrl: null
    #targetGroupIds: ""
    +"____pimcore_cache_item__": "document_162"
    dependencies: null
    __dataVersionTimestamp: 1738759478
    path: "/Data-Citation/"
    properties: [
      "blog_default_document" => Pimcore\Model\Property {#1891}
      "event_default_document" => Pimcore\Model\Property {#1885}
      "fallback_newsimg" => Pimcore\Model\Property {#1884}
      "language" => Pimcore\Model\Property {#1879}
      "navigation_root" => Pimcore\Model\Property {#1880}
      "news_default_document" => Pimcore\Model\Property {#1881}
      "project_default_document" => Pimcore\Model\Property {#1882}
      "rdresource_default_document" => Pimcore\Model\Property {#1878}
      "resource_default_document" => Pimcore\Model\Property {#1876}
      "sp_default_document" => Pimcore\Model\Property {#1875}
      "citation_start_doc" => Pimcore\Model\Property {#1874}
      "navigation_name" => Pimcore\Model\Property {#1873}
    ]
    id: 162
    creationDate: 1738759452
    modificationDate: 1738759478
    versionCount: 3
    userOwner: 2
    locked: null
    userModification: 2
    parentId: 160
    parent: null
    _fulldump: false
    o_dirtyFields: null
    fullPathCache: "/Recommendations-for-Data-Repositories"
    type: "page"
    key: "Recommendations-for-Data-Repositories"
    index: 2
    published: true
    children: []
    hasChildren: []
    siblings: []
    hasSiblings: []
    controller: "App\Controller\ContentController::dataCitationAction"
    template: null
    editables: [
      "contentblock" => Pimcore\Model\Document\Editable\Block {#3475}
      "contentblock:1.content" => Pimcore\Model\Document\Editable\Wysiwyg {#3474}
      "headline" => Pimcore\Model\Document\Editable\Input {#3480}
      "main_content" => Pimcore\Model\Document\Editable\Areablock {#3476}
    ]
    versions: null
    contentMasterDocumentId: null
    supportsContentMaster: true
    missingRequiredEditable: null
    staticGeneratorEnabled: null
    staticGeneratorLifetime: null
    inheritedEditables: []
    scheduledTasks: null
    title: "Recommendations for Data Repositories"
    description: ""
    metaData: []
    prettyUrl: null
    targetGroupIds: ""
  }
}

Request Headers

Header Value
accept 
"text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7"
accept-encoding 
"gzip, deflate, br, zstd"
accept-language 
"nb-NO,nb;q=0.9,en-GB;q=0.8,en;q=0.7,no;q=0.6,nn;q=0.5,en-US;q=0.4"
cache-control 
"max-age=0"
content-length 
""
content-type 
""
cookie 
"PHPSESSID=tudppbmflqfr15qnpb36e2rjnv; pimcore_admin_sid=1"
dnt 
"1"
host 
"datacitation.openconcept.no"
priority 
"u=0, i"
referer 
"https://datacitation.openconcept.no/"
sec-ch-ua 
""Not A(Brand";v="8", "Chromium";v="132", "Google Chrome";v="132""
sec-ch-ua-mobile 
"?0"
sec-ch-ua-platform 
""Windows""
sec-fetch-dest 
"document"
sec-fetch-mode 
"navigate"
sec-fetch-site 
"same-origin"
sec-fetch-user 
"?1"
upgrade-insecure-requests 
"1"
user-agent 
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36"
x-php-ob-level 
"1"

Request Content

Request content not available (it was retrieved as a resource).

Response

Response Headers

Header Value
cache-control 
"private, must-revalidate"
content-language 
"en"
content-type 
"text/html; charset=UTF-8"
date 
"Thu, 06 Feb 2025 07:09:13 GMT"
expires 
"Tue, 01 Jan 1980 00:00:00 GMT"
pragma 
"no-cache"
x-debug-token 
"8c4fb6"
x-powered-by 
"pimcore"

Cookies

Request Cookies

Key Value
PHPSESSID 
"tudppbmflqfr15qnpb36e2rjnv"
pimcore_admin_sid 
"1"

Response Cookies

No response cookies

Session

Session Metadata

No session metadata

Session Attributes

No session attributes

Session Usage

0 Usages
Stateless check enabled

Session not used.

Flashes

Flashes

No flash messages were created.

Server Parameters

Server Parameters

Defined in .env

Key Value
APP_ENV 
"dev"

Defined as regular env variables

Key Value
APP_DEBUG 
"1"
CONTENT_LENGTH 
""
CONTENT_TYPE 
""
DOCUMENT_ROOT 
"/sites/pimcore/cessda-dev/public"
DOCUMENT_URI 
"/index.php"
FCGI_ROLE 
"RESPONDER"
GATEWAY_INTERFACE 
"CGI/1.1"
HOME 
"/var/www"
HTTPS 
"on"
HTTP_ACCEPT 
"text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7"
HTTP_ACCEPT_ENCODING 
"gzip, deflate, br, zstd"
HTTP_ACCEPT_LANGUAGE 
"nb-NO,nb;q=0.9,en-GB;q=0.8,en;q=0.7,no;q=0.6,nn;q=0.5,en-US;q=0.4"
HTTP_CACHE_CONTROL 
"max-age=0"
HTTP_COOKIE 
"PHPSESSID=tudppbmflqfr15qnpb36e2rjnv; pimcore_admin_sid=1"
HTTP_DNT 
"1"
HTTP_HOST 
"datacitation.openconcept.no"
HTTP_PRIORITY 
"u=0, i"
HTTP_REFERER 
"https://datacitation.openconcept.no/"
HTTP_SEC_CH_UA 
""Not A(Brand";v="8", "Chromium";v="132", "Google Chrome";v="132""
HTTP_SEC_CH_UA_MOBILE 
"?0"
HTTP_SEC_CH_UA_PLATFORM 
""Windows""
HTTP_SEC_FETCH_DEST 
"document"
HTTP_SEC_FETCH_MODE 
"navigate"
HTTP_SEC_FETCH_SITE 
"same-origin"
HTTP_SEC_FETCH_USER 
"?1"
HTTP_UPGRADE_INSECURE_REQUESTS 
"1"
HTTP_USER_AGENT 
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36"
PATH_INFO 
""
PHP_SELF 
""
QUERY_STRING 
""
REDIRECT_STATUS 
"200"
REMOTE_ADDR 
"141.0.252.107"
REMOTE_PORT 
"61176"
REQUEST_METHOD 
"GET"
REQUEST_SCHEME 
"https"
REQUEST_TIME 
1738825753
REQUEST_TIME_FLOAT 
1738825753.0841
REQUEST_URI 
"/Recommendations-for-Data-Repositories"
SCRIPT_FILENAME 
"/sites/pimcore/cessda-dev/public/index.php"
SCRIPT_NAME 
"/index.php"
SERVER_ADDR 
"92.205.162.150"
SERVER_NAME 
"datacitation.openconcept.no"
SERVER_PORT 
"443"
SERVER_PROTOCOL 
"HTTP/2.0"
SERVER_SOFTWARE 
"nginx/1.27.1"
SYMFONY_DOTENV_VARS 
"APP_ENV"
USER 
"www-data"