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 {#1815 #container: Symfony\Component\DependencyInjection\Argument\ServiceLocator {#1813 …} } |
_locale | null |
_pimcore_context | "default" |
_pimcore_frontend_request | true |
_route | "document_164" |
_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" : 1 : [ "" ] : 160 : Pimcore\Model\Document\Page {#1639 …} : null : "datacitation.openconcept.no" : "/Errorpage" : [ "en" => "/Errorpage" ] : false : 1738654614 : 1738654614 } |
_site_path | "/Data-Citation/Recommendations-for-Journals-and-Publishers" |
_stopwatch_token | "ad24dd" |
_template | Sensio\Bundle\FrameworkExtraBundle\Configuration\Template {#2570 #template: "content/data_citation.html.twig" -vars: [] -streamable: false -owner: [ App\Controller\ContentController {#1815 #container: Symfony\Component\DependencyInjection\Argument\ServiceLocator {#1813 …} } "dataCitationAction" ] } |
contentDocument | Pimcore\Model\Document\Page {#1894 #dao: Pimcore\Model\Document\Page\Dao {#1858 …} #dependencies: null #__dataVersionTimestamp: 1738826002 #path: "/Data-Citation/" #properties: [ "blog_default_document" => Pimcore\Model\Property {#1876 #dao: null #name: "blog_default_document" #data: "51" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "blog_default_document" : "51" : "document" : "document" : null : 164 : true : true } "event_default_document" => Pimcore\Model\Property {#1860 #dao: null #name: "event_default_document" #data: "44" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "event_default_document" : "44" : "document" : "document" : null : 164 : true : true } "fallback_newsimg" => Pimcore\Model\Property {#1870 #dao: null #name: "fallback_newsimg" #data: "488" #type: "asset" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "fallback_newsimg" : "488" : "asset" : "document" : null : 164 : true : true } "language" => Pimcore\Model\Property {#1871 #dao: null #name: "language" #data: null #type: "text" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "language" : null : "text" : "document" : null : 164 : true : true } "navigation_root" => Pimcore\Model\Property {#1874 #dao: null #name: "navigation_root" #data: "1" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "navigation_root" : "1" : "document" : "document" : null : 164 : true : true } "news_default_document" => Pimcore\Model\Property {#1879 #dao: null #name: "news_default_document" #data: "43" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "news_default_document" : "43" : "document" : "document" : null : 164 : true : true } "project_default_document" => Pimcore\Model\Property {#1880 #dao: null #name: "project_default_document" #data: "25" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "project_default_document" : "25" : "document" : "document" : null : 164 : true : true } "rdresource_default_document" => Pimcore\Model\Property {#1866 #dao: null #name: "rdresource_default_document" #data: "159" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "rdresource_default_document" : "159" : "document" : "document" : null : 164 : true : true } "resource_default_document" => Pimcore\Model\Property {#1885 #dao: null #name: "resource_default_document" #data: "6" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "resource_default_document" : "6" : "document" : "document" : null : 164 : true : true } "sp_default_document" => Pimcore\Model\Property {#1884 #dao: null #name: "sp_default_document" #data: "56" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "sp_default_document" : "56" : "document" : "document" : null : 164 : true : true } "citation_start_doc" => Pimcore\Model\Property {#1882 #dao: null #name: "citation_start_doc" #data: "160" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "citation_start_doc" : "160" : "document" : "document" : null : 164 : true : true } "navigation_name" => Pimcore\Model\Property {#1865 #dao: null #name: "navigation_name" #data: "Recommendations for Journals and Publishers" #type: "text" #ctype: "document" #cpath: null #cid: 164 #inheritable: false #inherited: false : "navigation_name" : "Recommendations for Journals and Publishers" : "text" : "document" : null : 164 : false : false } ] #id: 164 #creationDate: 1738759542 #modificationDate: 1738826002 #versionCount: 5 #userOwner: 2 #locked: null #userModification: 2 #parentId: 160 #parent: Pimcore\Model\Document\Page {#1869 …} #_fulldump: false #o_dirtyFields: null -activeDispatchingEvents: [] #fullPathCache: "/Recommendations-for-Journals-and-Publishers" #type: "page" #key: "Recommendations-for-Journals-and-Publishers" #index: 4 #published: true #children: [] #hasChildren: [] #siblings: [] #hasSiblings: [] #controller: "App\Controller\ContentController::dataCitationAction" #template: null #editables: [ "contentblock" => Pimcore\Model\Document\Editable\Block {#3070 #dao: null #config: null #name: "contentblock" #realName: null -parentBlockNames: [] #documentId: 164 #document: Pimcore\Model\Document\Page {#1894} #editmode: null #inherited: false #inDialogBox: null -editableDefinitionCollector: null #indices: [] #current: 0 : null : "contentblock" : null : 164 : Pimcore\Model\Document\Page {#1894} : null : false : null : [] : 0 } "contentblock:1.content" => Pimcore\Model\Document\Editable\Wysiwyg {#3078 #dao: null #config: null #name: "contentblock:1.content" #realName: null -parentBlockNames: [] #documentId: 164 #document: Pimcore\Model\Document\Page {#1894} #editmode: null #inherited: false #inDialogBox: null -editableDefinitionCollector: null #text: "" : null : "contentblock:1.content" : null : 164 : Pimcore\Model\Document\Page {#1894} : null : false : null : "" } "headline" => Pimcore\Model\Document\Editable\Input {#3081 #dao: null #config: [ "placeholder" => "Headline" "width" => 600 ] #name: "headline" #realName: "headline" -parentBlockNames: [] #documentId: 164 #document: Pimcore\Model\Document\Page {#1894} #editmode: false #inherited: false #inDialogBox: null -editableDefinitionCollector: null #text: "Recommendations for Journals and Publishers" : [ "placeholder" => "Headline" "width" => 600 ] : "headline" : "headline" : 164 : Pimcore\Model\Document\Page {#1894} : false : false : null : "Recommendations for Journals and Publishers" } "main_content" => Pimcore\Model\Document\Editable\Areablock {#3086 #dao: null #config: [ "allowed" => [ "video" "wysiwyg" "text-accordion" ] "sorting" => [ "wysiwyg" "text-accordion" "video" ] "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 ] ] "limit" => 1000000 "blockStateStack" => "[{"blocks":[],"indexes":[]}]" ] #name: "main_content" #realName: "main_content" -parentBlockNames: [] #documentId: 164 #document: Pimcore\Model\Document\Page {#1894} #editmode: false #inherited: false #inDialogBox: null -editableDefinitionCollector: null #indices: [ [ "key" => "1" "type" => "wysiwyg" "hidden" => false ] ] #current: 0 #currentIndex: [ "key" => "1" "type" => "wysiwyg" "hidden" => false ] #blockStarted: false #brickTypeUsageCounter: [ "wysiwyg" => 1 ] : [ "allowed" => [ "video" "wysiwyg" "text-accordion" ] "sorting" => [ "wysiwyg" "text-accordion" "video" ] "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 ] ] "limit" => 1000000 "blockStateStack" => "[{"blocks":[],"indexes":[]}]" ] : "main_content" : "main_content" : 164 : Pimcore\Model\Document\Page {#1894} : false : false : null : [ [ "key" => "1" "type" => "wysiwyg" "hidden" => false ] ] : 0 : [ "key" => "1" "type" => "wysiwyg" "hidden" => false ] : false : [ "wysiwyg" => 1 ] } "main_content:1.content" => Pimcore\Model\Document\Editable\Wysiwyg {#3082 #dao: null #config: [] #name: "main_content:1.content" #realName: "content" -parentBlockNames: [] #documentId: 164 #document: Pimcore\Model\Document\Page {#1894} #editmode: false #inherited: false #inDialogBox: null -editableDefinitionCollector: null #text: """ <h3>Recommendation 1 – Allow data citations in the standard list of references</h3>\n \n <p>Journals should allow citations of data or replication materials (such as software or project files) to be listed together with other references in the standard reference list of an article.</p>\n \n <p>Journals should not limit authors to only mentioning or citing the data in the Data Availability Statement (DAS), or in the acknowledgement section. DAS sections are useful to clarify how data might be accessed or requested. However, they do not mitigate the need for a full data citation in the reference list. The DAS section is rarely usable as a machine-readable metadata source, and will often be ignored by metadata indexing.</p>\n \n <p>Reference lists are an important metadata source for citation indexing, metrics and relational mapping. Excluding cited data from reference lists limits the findability, reach and possible reuse of a data publication, limits machine readability, and creates fewer incentives for authors to publish FAIR data.</p>\n \n <h3><a name="_ghjxe4tkkuis"></a>Recommendation 2 – Require authors to cite data specifically</h3>\n \n <p>Journals should require authors to cite any data, whether they are simply mentioned in the manuscript or underlying their results. This also includes complete datasets or partial datasets necessary for replication purposes, for instance. They should instruct authors to cite actual data publications when available, and not only publications relating to the data (such as methodological reports, data articles, etc.). The data must be cited specifically in the text and in the reference list, regardless if it is primary material (developed by the article’s authors) or secondary material (developed by other researchers). As a specific type of primary material, replication materials such as code, software, or project files should also be cited specifically in relevant sections of the text and in the reference list.</p>\n \n <h3><a name="_28olxvcoih3w"></a>Recommendation 3 – Include all six core components in data citations and provide citation examples</h3>\n \n <p>Journals should choose reference styles with rules that do not prevent the inclusion of all six core components of a data citation in the reference list. Moreover, journals should provide clear examples of well-formed data citations including all core components in their submission guidelines for authors.</p>\n \n <p>While most reference styles accommodate authors, title, publication year, publisher, and the inclusion of a URL, certain components specific to data citations – such as the version (a core component) or resource type (an additional component) – may not be directly supported. In such cases, these details can be incorporated into the title field.</p>\n \n <h3><a name="_nvuzmy1atj02"></a>Recommendation 4 – Encourage authors to publish data and replication materials as independent publications</h3>\n \n <p>Journals should encourage authors to publish related data and replication materials as independent publications in suitable repositories. Both open and restricted data publications should follow the FAIR data principles. Merely stating in the article that data are available upon request does not qualify as an independent data publication.</p>\n \n <p>Journals should not consider data or replication materials to be mere supplements or appendices to an article. Moreover, they should not encourage authors to upload supplement file attachments to journal publishing platforms as an alternative to independent publishing in a data repository or code repository. Data hidden away in supplement file attachments will have limited visibility for indexing and will rarely fulfil the FAIR data principles. It should however be noted that some publisher infrastructures do provide suitable data repositories for making independent data publications.</p>\n \n <p>If data and replication materials are both available, journals should suggest that authors publish them as separate publications. If it is not possible to publish data with open access, they should encourage authors to make formal and independent publications of data with restricted access. Both the replication materials and the data should, if possible, refer to each other using full citations as well as PIDs. This is preferable to a single publication containing both data and replication materials. Separate publications will allow better addressability in citations and encourage a modular and reusable approach to replication packaging. In some cases, a modular approach will allow sharing of replication materials as an independent publication with open access, while access to the data or subset of data themselves may be restricted. However, in certain cases packaging and publishing both data and replication materials as a single publication might be a better option because of requirements in certain workflows or standards.</p>\n \n <h3><a name="_75nehig3drj5"></a>Recommendation 5 - Encourage authors to provide PIDs for published data and replication materials</h3>\n \n <p>Journals should also encourage authors to provide persistent identifiers (PIDs) for published data and replication materials when submitting content. This enables stable and unambiguous references to such publications, which is also why a PID is one of the six core components of a data citation. Authors may use dedicated repository services that provide PIDs or register them using other means, such as through specific research infrastructures or automated workflows providing PID assignments. PIDs should be provided for open-access data publications as well as for restricted data publications where only metadata may be publicly available. Generic sample numbers and other identifiers that are not machine-actionable do not qualify as PIDs.</p>\n \n <h3><a name="_lg441o2e7xyo"></a>Recommendation 6 - Allow sufficient time for quality assurance and data curation</h3>\n \n <p>Journals and authors should be aware that formal data publications in trusted data repositories often need to pass through review and quality assurance. They should inform authors that they should expect a curation process before the data publication is made publicly available. Journals should account for this curation process, which may require several amendments before being approved, similar to the peer review process of a journal manuscript. To streamline publication timelines, journals should encourage researchers to deposit their data and replication materials before or during the article review process (e.g., after the first peer review), and if needed make the data and replication materials accessible only to the reviewers during the article review process. This ensures that by the time the article is ready for publication, the data and the final version of the replication materials are also ready to be published or have already been published.</p>\n """ : [] : "main_content:1.content" : "content" : 164 : Pimcore\Model\Document\Page {#1894} : false : false : null : """ <h3>Recommendation 1 – Allow data citations in the standard list of references</h3>\n \n <p>Journals should allow citations of data or replication materials (such as software or project files) to be listed together with other references in the standard reference list of an article.</p>\n \n <p>Journals should not limit authors to only mentioning or citing the data in the Data Availability Statement (DAS), or in the acknowledgement section. DAS sections are useful to clarify how data might be accessed or requested. However, they do not mitigate the need for a full data citation in the reference list. The DAS section is rarely usable as a machine-readable metadata source, and will often be ignored by metadata indexing.</p>\n \n <p>Reference lists are an important metadata source for citation indexing, metrics and relational mapping. Excluding cited data from reference lists limits the findability, reach and possible reuse of a data publication, limits machine readability, and creates fewer incentives for authors to publish FAIR data.</p>\n \n <h3><a name="_ghjxe4tkkuis"></a>Recommendation 2 – Require authors to cite data specifically</h3>\n \n <p>Journals should require authors to cite any data, whether they are simply mentioned in the manuscript or underlying their results. This also includes complete datasets or partial datasets necessary for replication purposes, for instance. They should instruct authors to cite actual data publications when available, and not only publications relating to the data (such as methodological reports, data articles, etc.). The data must be cited specifically in the text and in the reference list, regardless if it is primary material (developed by the article’s authors) or secondary material (developed by other researchers). As a specific type of primary material, replication materials such as code, software, or project files should also be cited specifically in relevant sections of the text and in the reference list.</p>\n \n <h3><a name="_28olxvcoih3w"></a>Recommendation 3 – Include all six core components in data citations and provide citation examples</h3>\n \n <p>Journals should choose reference styles with rules that do not prevent the inclusion of all six core components of a data citation in the reference list. Moreover, journals should provide clear examples of well-formed data citations including all core components in their submission guidelines for authors.</p>\n \n <p>While most reference styles accommodate authors, title, publication year, publisher, and the inclusion of a URL, certain components specific to data citations – such as the version (a core component) or resource type (an additional component) – may not be directly supported. In such cases, these details can be incorporated into the title field.</p>\n \n <h3><a name="_nvuzmy1atj02"></a>Recommendation 4 – Encourage authors to publish data and replication materials as independent publications</h3>\n \n <p>Journals should encourage authors to publish related data and replication materials as independent publications in suitable repositories. Both open and restricted data publications should follow the FAIR data principles. Merely stating in the article that data are available upon request does not qualify as an independent data publication.</p>\n \n <p>Journals should not consider data or replication materials to be mere supplements or appendices to an article. Moreover, they should not encourage authors to upload supplement file attachments to journal publishing platforms as an alternative to independent publishing in a data repository or code repository. Data hidden away in supplement file attachments will have limited visibility for indexing and will rarely fulfil the FAIR data principles. It should however be noted that some publisher infrastructures do provide suitable data repositories for making independent data publications.</p>\n \n <p>If data and replication materials are both available, journals should suggest that authors publish them as separate publications. If it is not possible to publish data with open access, they should encourage authors to make formal and independent publications of data with restricted access. Both the replication materials and the data should, if possible, refer to each other using full citations as well as PIDs. This is preferable to a single publication containing both data and replication materials. Separate publications will allow better addressability in citations and encourage a modular and reusable approach to replication packaging. In some cases, a modular approach will allow sharing of replication materials as an independent publication with open access, while access to the data or subset of data themselves may be restricted. However, in certain cases packaging and publishing both data and replication materials as a single publication might be a better option because of requirements in certain workflows or standards.</p>\n \n <h3><a name="_75nehig3drj5"></a>Recommendation 5 - Encourage authors to provide PIDs for published data and replication materials</h3>\n \n <p>Journals should also encourage authors to provide persistent identifiers (PIDs) for published data and replication materials when submitting content. This enables stable and unambiguous references to such publications, which is also why a PID is one of the six core components of a data citation. Authors may use dedicated repository services that provide PIDs or register them using other means, such as through specific research infrastructures or automated workflows providing PID assignments. PIDs should be provided for open-access data publications as well as for restricted data publications where only metadata may be publicly available. Generic sample numbers and other identifiers that are not machine-actionable do not qualify as PIDs.</p>\n \n <h3><a name="_lg441o2e7xyo"></a>Recommendation 6 - Allow sufficient time for quality assurance and data curation</h3>\n \n <p>Journals and authors should be aware that formal data publications in trusted data repositories often need to pass through review and quality assurance. They should inform authors that they should expect a curation process before the data publication is made publicly available. Journals should account for this curation process, which may require several amendments before being approved, similar to the peer review process of a journal manuscript. To streamline publication timelines, journals should encourage researchers to deposit their data and replication materials before or during the article review process (e.g., after the first peer review), and if needed make the data and replication materials accessible only to the reviewers during the article review process. This ensures that by the time the article is ready for publication, the data and the final version of the replication materials are also ready to be published or have already been published.</p>\n """ } ] #versions: null #contentMasterDocumentId: null #supportsContentMaster: true #missingRequiredEditable: null #staticGeneratorEnabled: null #staticGeneratorLifetime: null #inheritedEditables: [] #scheduledTasks: null -useTargetGroup: null #title: "Recommendations for Journals and Publishers" #description: "" #metaData: [] #prettyUrl: null #targetGroupIds: "" +"____pimcore_cache_item__": "document_164" : null : 1738826002 : "/Data-Citation/" : [ "blog_default_document" => Pimcore\Model\Property {#1876} "event_default_document" => Pimcore\Model\Property {#1860} "fallback_newsimg" => Pimcore\Model\Property {#1870} "language" => Pimcore\Model\Property {#1871} "navigation_root" => Pimcore\Model\Property {#1874} "news_default_document" => Pimcore\Model\Property {#1879} "project_default_document" => Pimcore\Model\Property {#1880} "rdresource_default_document" => Pimcore\Model\Property {#1866} "resource_default_document" => Pimcore\Model\Property {#1885} "sp_default_document" => Pimcore\Model\Property {#1884} "citation_start_doc" => Pimcore\Model\Property {#1882} "navigation_name" => Pimcore\Model\Property {#1865} ] : 164 : 1738759542 : 1738826002 : 5 : 2 : null : 2 : 160 : Pimcore\Model\Document\Page {#1869 …} : false : null : "/Recommendations-for-Journals-and-Publishers" : "page" : "Recommendations-for-Journals-and-Publishers" : 4 : true : [] : [] : [] : [] : "App\Controller\ContentController::dataCitationAction" : null : [ "contentblock" => Pimcore\Model\Document\Editable\Block {#3070} "contentblock:1.content" => Pimcore\Model\Document\Editable\Wysiwyg {#3078} "headline" => Pimcore\Model\Document\Editable\Input {#3081} "main_content" => Pimcore\Model\Document\Editable\Areablock {#3086} "main_content:1.content" => Pimcore\Model\Document\Editable\Wysiwyg {#3082} ] : null : null : true : null : null : null : [] : null : "Recommendations for Journals and Publishers" : "" : [] : null : "" } |
routeDocument | Pimcore\Routing\DocumentRoute {#1877 -path: "/Recommendations-for-Journals-and-Publishers" -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 {#1857 …} #document: Pimcore\Model\Document\Page {#1894 #dao: Pimcore\Model\Document\Page\Dao {#1858 …} #dependencies: null #__dataVersionTimestamp: 1738826002 #path: "/Data-Citation/" #properties: [ "blog_default_document" => Pimcore\Model\Property {#1876 #dao: null #name: "blog_default_document" #data: "51" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "blog_default_document" : "51" : "document" : "document" : null : 164 : true : true } "event_default_document" => Pimcore\Model\Property {#1860 #dao: null #name: "event_default_document" #data: "44" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "event_default_document" : "44" : "document" : "document" : null : 164 : true : true } "fallback_newsimg" => Pimcore\Model\Property {#1870 #dao: null #name: "fallback_newsimg" #data: "488" #type: "asset" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "fallback_newsimg" : "488" : "asset" : "document" : null : 164 : true : true } "language" => Pimcore\Model\Property {#1871 #dao: null #name: "language" #data: null #type: "text" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "language" : null : "text" : "document" : null : 164 : true : true } "navigation_root" => Pimcore\Model\Property {#1874 #dao: null #name: "navigation_root" #data: "1" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "navigation_root" : "1" : "document" : "document" : null : 164 : true : true } "news_default_document" => Pimcore\Model\Property {#1879 #dao: null #name: "news_default_document" #data: "43" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "news_default_document" : "43" : "document" : "document" : null : 164 : true : true } "project_default_document" => Pimcore\Model\Property {#1880 #dao: null #name: "project_default_document" #data: "25" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "project_default_document" : "25" : "document" : "document" : null : 164 : true : true } "rdresource_default_document" => Pimcore\Model\Property {#1866 #dao: null #name: "rdresource_default_document" #data: "159" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "rdresource_default_document" : "159" : "document" : "document" : null : 164 : true : true } "resource_default_document" => Pimcore\Model\Property {#1885 #dao: null #name: "resource_default_document" #data: "6" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "resource_default_document" : "6" : "document" : "document" : null : 164 : true : true } "sp_default_document" => Pimcore\Model\Property {#1884 #dao: null #name: "sp_default_document" #data: "56" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "sp_default_document" : "56" : "document" : "document" : null : 164 : true : true } "citation_start_doc" => Pimcore\Model\Property {#1882 #dao: null #name: "citation_start_doc" #data: "160" #type: "document" #ctype: "document" #cpath: null #cid: 164 #inheritable: true #inherited: true : "citation_start_doc" : "160" : "document" : "document" : null : 164 : true : true } "navigation_name" => Pimcore\Model\Property {#1865 #dao: null #name: "navigation_name" #data: "Recommendations for Journals and Publishers" #type: "text" #ctype: "document" #cpath: null #cid: 164 #inheritable: false #inherited: false : "navigation_name" : "Recommendations for Journals and Publishers" : "text" : "document" : null : 164 : false : false } ] #id: 164 #creationDate: 1738759542 #modificationDate: 1738826002 #versionCount: 5 #userOwner: 2 #locked: null #userModification: 2 #parentId: 160 #parent: Pimcore\Model\Document\Page {#1869 …} #_fulldump: false #o_dirtyFields: null -activeDispatchingEvents: [] #fullPathCache: "/Recommendations-for-Journals-and-Publishers" #type: "page" #key: "Recommendations-for-Journals-and-Publishers" #index: 4 #published: true #children: [] #hasChildren: [] #siblings: [] #hasSiblings: [] #controller: "App\Controller\ContentController::dataCitationAction" #template: null #editables: [ "contentblock" => Pimcore\Model\Document\Editable\Block {#3070 #dao: null #config: null #name: "contentblock" #realName: null -parentBlockNames: [] #documentId: 164 #document: Pimcore\Model\Document\Page {#1894} #editmode: null #inherited: false #inDialogBox: null -editableDefinitionCollector: null #indices: [] #current: 0 : null : "contentblock" : null : 164 : Pimcore\Model\Document\Page {#1894} : null : false : null : [] : 0 } "contentblock:1.content" => Pimcore\Model\Document\Editable\Wysiwyg {#3078 #dao: null #config: null #name: "contentblock:1.content" #realName: null -parentBlockNames: [] #documentId: 164 #document: Pimcore\Model\Document\Page {#1894} #editmode: null #inherited: false #inDialogBox: null -editableDefinitionCollector: null #text: "" : null : "contentblock:1.content" : null : 164 : Pimcore\Model\Document\Page {#1894} : null : false : null : "" } "headline" => Pimcore\Model\Document\Editable\Input {#3081 #dao: null #config: [ "placeholder" => "Headline" "width" => 600 ] #name: "headline" #realName: "headline" -parentBlockNames: [] #documentId: 164 #document: Pimcore\Model\Document\Page {#1894} #editmode: false #inherited: false #inDialogBox: null -editableDefinitionCollector: null #text: "Recommendations for Journals and Publishers" : [ "placeholder" => "Headline" "width" => 600 ] : "headline" : "headline" : 164 : Pimcore\Model\Document\Page {#1894} : false : false : null : "Recommendations for Journals and Publishers" } "main_content" => Pimcore\Model\Document\Editable\Areablock {#3086 #dao: null #config: [ "allowed" => [ "video" "wysiwyg" "text-accordion" ] "sorting" => [ "wysiwyg" "text-accordion" "video" ] "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 ] ] "limit" => 1000000 "blockStateStack" => "[{"blocks":[],"indexes":[]}]" ] #name: "main_content" #realName: "main_content" -parentBlockNames: [] #documentId: 164 #document: Pimcore\Model\Document\Page {#1894} #editmode: false #inherited: false #inDialogBox: null -editableDefinitionCollector: null #indices: [ [ "key" => "1" "type" => "wysiwyg" "hidden" => false ] ] #current: 0 #currentIndex: [ "key" => "1" "type" => "wysiwyg" "hidden" => false ] #blockStarted: false #brickTypeUsageCounter: [ "wysiwyg" => 1 ] : [ "allowed" => [ "video" "wysiwyg" "text-accordion" ] "sorting" => [ "wysiwyg" "text-accordion" "video" ] "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 ] ] "limit" => 1000000 "blockStateStack" => "[{"blocks":[],"indexes":[]}]" ] : "main_content" : "main_content" : 164 : Pimcore\Model\Document\Page {#1894} : false : false : null : [ [ "key" => "1" "type" => "wysiwyg" "hidden" => false ] ] : 0 : [ "key" => "1" "type" => "wysiwyg" "hidden" => false ] : false : [ "wysiwyg" => 1 ] } "main_content:1.content" => Pimcore\Model\Document\Editable\Wysiwyg {#3082 #dao: null #config: [] #name: "main_content:1.content" #realName: "content" -parentBlockNames: [] #documentId: 164 #document: Pimcore\Model\Document\Page {#1894} #editmode: false #inherited: false #inDialogBox: null -editableDefinitionCollector: null #text: """ <h3>Recommendation 1 – Allow data citations in the standard list of references</h3>\n \n <p>Journals should allow citations of data or replication materials (such as software or project files) to be listed together with other references in the standard reference list of an article.</p>\n \n <p>Journals should not limit authors to only mentioning or citing the data in the Data Availability Statement (DAS), or in the acknowledgement section. DAS sections are useful to clarify how data might be accessed or requested. However, they do not mitigate the need for a full data citation in the reference list. The DAS section is rarely usable as a machine-readable metadata source, and will often be ignored by metadata indexing.</p>\n \n <p>Reference lists are an important metadata source for citation indexing, metrics and relational mapping. Excluding cited data from reference lists limits the findability, reach and possible reuse of a data publication, limits machine readability, and creates fewer incentives for authors to publish FAIR data.</p>\n \n <h3><a name="_ghjxe4tkkuis"></a>Recommendation 2 – Require authors to cite data specifically</h3>\n \n <p>Journals should require authors to cite any data, whether they are simply mentioned in the manuscript or underlying their results. This also includes complete datasets or partial datasets necessary for replication purposes, for instance. They should instruct authors to cite actual data publications when available, and not only publications relating to the data (such as methodological reports, data articles, etc.). The data must be cited specifically in the text and in the reference list, regardless if it is primary material (developed by the article’s authors) or secondary material (developed by other researchers). As a specific type of primary material, replication materials such as code, software, or project files should also be cited specifically in relevant sections of the text and in the reference list.</p>\n \n <h3><a name="_28olxvcoih3w"></a>Recommendation 3 – Include all six core components in data citations and provide citation examples</h3>\n \n <p>Journals should choose reference styles with rules that do not prevent the inclusion of all six core components of a data citation in the reference list. Moreover, journals should provide clear examples of well-formed data citations including all core components in their submission guidelines for authors.</p>\n \n <p>While most reference styles accommodate authors, title, publication year, publisher, and the inclusion of a URL, certain components specific to data citations – such as the version (a core component) or resource type (an additional component) – may not be directly supported. In such cases, these details can be incorporated into the title field.</p>\n \n <h3><a name="_nvuzmy1atj02"></a>Recommendation 4 – Encourage authors to publish data and replication materials as independent publications</h3>\n \n <p>Journals should encourage authors to publish related data and replication materials as independent publications in suitable repositories. Both open and restricted data publications should follow the FAIR data principles. Merely stating in the article that data are available upon request does not qualify as an independent data publication.</p>\n \n <p>Journals should not consider data or replication materials to be mere supplements or appendices to an article. Moreover, they should not encourage authors to upload supplement file attachments to journal publishing platforms as an alternative to independent publishing in a data repository or code repository. Data hidden away in supplement file attachments will have limited visibility for indexing and will rarely fulfil the FAIR data principles. It should however be noted that some publisher infrastructures do provide suitable data repositories for making independent data publications.</p>\n \n <p>If data and replication materials are both available, journals should suggest that authors publish them as separate publications. If it is not possible to publish data with open access, they should encourage authors to make formal and independent publications of data with restricted access. Both the replication materials and the data should, if possible, refer to each other using full citations as well as PIDs. This is preferable to a single publication containing both data and replication materials. Separate publications will allow better addressability in citations and encourage a modular and reusable approach to replication packaging. In some cases, a modular approach will allow sharing of replication materials as an independent publication with open access, while access to the data or subset of data themselves may be restricted. However, in certain cases packaging and publishing both data and replication materials as a single publication might be a better option because of requirements in certain workflows or standards.</p>\n \n <h3><a name="_75nehig3drj5"></a>Recommendation 5 - Encourage authors to provide PIDs for published data and replication materials</h3>\n \n <p>Journals should also encourage authors to provide persistent identifiers (PIDs) for published data and replication materials when submitting content. This enables stable and unambiguous references to such publications, which is also why a PID is one of the six core components of a data citation. Authors may use dedicated repository services that provide PIDs or register them using other means, such as through specific research infrastructures or automated workflows providing PID assignments. PIDs should be provided for open-access data publications as well as for restricted data publications where only metadata may be publicly available. Generic sample numbers and other identifiers that are not machine-actionable do not qualify as PIDs.</p>\n \n <h3><a name="_lg441o2e7xyo"></a>Recommendation 6 - Allow sufficient time for quality assurance and data curation</h3>\n \n <p>Journals and authors should be aware that formal data publications in trusted data repositories often need to pass through review and quality assurance. They should inform authors that they should expect a curation process before the data publication is made publicly available. Journals should account for this curation process, which may require several amendments before being approved, similar to the peer review process of a journal manuscript. To streamline publication timelines, journals should encourage researchers to deposit their data and replication materials before or during the article review process (e.g., after the first peer review), and if needed make the data and replication materials accessible only to the reviewers during the article review process. This ensures that by the time the article is ready for publication, the data and the final version of the replication materials are also ready to be published or have already been published.</p>\n """ : [] : "main_content:1.content" : "content" : 164 : Pimcore\Model\Document\Page {#1894} : false : false : null : """ <h3>Recommendation 1 – Allow data citations in the standard list of references</h3>\n \n <p>Journals should allow citations of data or replication materials (such as software or project files) to be listed together with other references in the standard reference list of an article.</p>\n \n <p>Journals should not limit authors to only mentioning or citing the data in the Data Availability Statement (DAS), or in the acknowledgement section. DAS sections are useful to clarify how data might be accessed or requested. However, they do not mitigate the need for a full data citation in the reference list. The DAS section is rarely usable as a machine-readable metadata source, and will often be ignored by metadata indexing.</p>\n \n <p>Reference lists are an important metadata source for citation indexing, metrics and relational mapping. Excluding cited data from reference lists limits the findability, reach and possible reuse of a data publication, limits machine readability, and creates fewer incentives for authors to publish FAIR data.</p>\n \n <h3><a name="_ghjxe4tkkuis"></a>Recommendation 2 – Require authors to cite data specifically</h3>\n \n <p>Journals should require authors to cite any data, whether they are simply mentioned in the manuscript or underlying their results. This also includes complete datasets or partial datasets necessary for replication purposes, for instance. They should instruct authors to cite actual data publications when available, and not only publications relating to the data (such as methodological reports, data articles, etc.). The data must be cited specifically in the text and in the reference list, regardless if it is primary material (developed by the article’s authors) or secondary material (developed by other researchers). As a specific type of primary material, replication materials such as code, software, or project files should also be cited specifically in relevant sections of the text and in the reference list.</p>\n \n <h3><a name="_28olxvcoih3w"></a>Recommendation 3 – Include all six core components in data citations and provide citation examples</h3>\n \n <p>Journals should choose reference styles with rules that do not prevent the inclusion of all six core components of a data citation in the reference list. Moreover, journals should provide clear examples of well-formed data citations including all core components in their submission guidelines for authors.</p>\n \n <p>While most reference styles accommodate authors, title, publication year, publisher, and the inclusion of a URL, certain components specific to data citations – such as the version (a core component) or resource type (an additional component) – may not be directly supported. In such cases, these details can be incorporated into the title field.</p>\n \n <h3><a name="_nvuzmy1atj02"></a>Recommendation 4 – Encourage authors to publish data and replication materials as independent publications</h3>\n \n <p>Journals should encourage authors to publish related data and replication materials as independent publications in suitable repositories. Both open and restricted data publications should follow the FAIR data principles. Merely stating in the article that data are available upon request does not qualify as an independent data publication.</p>\n \n <p>Journals should not consider data or replication materials to be mere supplements or appendices to an article. Moreover, they should not encourage authors to upload supplement file attachments to journal publishing platforms as an alternative to independent publishing in a data repository or code repository. Data hidden away in supplement file attachments will have limited visibility for indexing and will rarely fulfil the FAIR data principles. It should however be noted that some publisher infrastructures do provide suitable data repositories for making independent data publications.</p>\n \n <p>If data and replication materials are both available, journals should suggest that authors publish them as separate publications. If it is not possible to publish data with open access, they should encourage authors to make formal and independent publications of data with restricted access. Both the replication materials and the data should, if possible, refer to each other using full citations as well as PIDs. This is preferable to a single publication containing both data and replication materials. Separate publications will allow better addressability in citations and encourage a modular and reusable approach to replication packaging. In some cases, a modular approach will allow sharing of replication materials as an independent publication with open access, while access to the data or subset of data themselves may be restricted. However, in certain cases packaging and publishing both data and replication materials as a single publication might be a better option because of requirements in certain workflows or standards.</p>\n \n <h3><a name="_75nehig3drj5"></a>Recommendation 5 - Encourage authors to provide PIDs for published data and replication materials</h3>\n \n <p>Journals should also encourage authors to provide persistent identifiers (PIDs) for published data and replication materials when submitting content. This enables stable and unambiguous references to such publications, which is also why a PID is one of the six core components of a data citation. Authors may use dedicated repository services that provide PIDs or register them using other means, such as through specific research infrastructures or automated workflows providing PID assignments. PIDs should be provided for open-access data publications as well as for restricted data publications where only metadata may be publicly available. Generic sample numbers and other identifiers that are not machine-actionable do not qualify as PIDs.</p>\n \n <h3><a name="_lg441o2e7xyo"></a>Recommendation 6 - Allow sufficient time for quality assurance and data curation</h3>\n \n <p>Journals and authors should be aware that formal data publications in trusted data repositories often need to pass through review and quality assurance. They should inform authors that they should expect a curation process before the data publication is made publicly available. Journals should account for this curation process, which may require several amendments before being approved, similar to the peer review process of a journal manuscript. To streamline publication timelines, journals should encourage researchers to deposit their data and replication materials before or during the article review process (e.g., after the first peer review), and if needed make the data and replication materials accessible only to the reviewers during the article review process. This ensures that by the time the article is ready for publication, the data and the final version of the replication materials are also ready to be published or have already been published.</p>\n """ } ] #versions: null #contentMasterDocumentId: null #supportsContentMaster: true #missingRequiredEditable: null #staticGeneratorEnabled: null #staticGeneratorLifetime: null #inheritedEditables: [] #scheduledTasks: null -useTargetGroup: null #title: "Recommendations for Journals and Publishers" #description: "" #metaData: [] #prettyUrl: null #targetGroupIds: "" +"____pimcore_cache_item__": "document_164" : null : 1738826002 : "/Data-Citation/" : [ "blog_default_document" => Pimcore\Model\Property {#1876} "event_default_document" => Pimcore\Model\Property {#1860} "fallback_newsimg" => Pimcore\Model\Property {#1870} "language" => Pimcore\Model\Property {#1871} "navigation_root" => Pimcore\Model\Property {#1874} "news_default_document" => Pimcore\Model\Property {#1879} "project_default_document" => Pimcore\Model\Property {#1880} "rdresource_default_document" => Pimcore\Model\Property {#1866} "resource_default_document" => Pimcore\Model\Property {#1885} "sp_default_document" => Pimcore\Model\Property {#1884} "citation_start_doc" => Pimcore\Model\Property {#1882} "navigation_name" => Pimcore\Model\Property {#1865} ] : 164 : 1738759542 : 1738826002 : 5 : 2 : null : 2 : 160 : Pimcore\Model\Document\Page {#1869 …} : false : null : "/Recommendations-for-Journals-and-Publishers" : "page" : "Recommendations-for-Journals-and-Publishers" : 4 : true : [] : [] : [] : [] : "App\Controller\ContentController::dataCitationAction" : null : [ "contentblock" => Pimcore\Model\Document\Editable\Block {#3070} "contentblock:1.content" => Pimcore\Model\Document\Editable\Wysiwyg {#3078} "headline" => Pimcore\Model\Document\Editable\Input {#3081} "main_content" => Pimcore\Model\Document\Editable\Areablock {#3086} "main_content:1.content" => Pimcore\Model\Document\Editable\Wysiwyg {#3082} ] : null : null : true : null : null : null : [] : null : "Recommendations for Journals and Publishers" : "" : [] : null : "" } } |
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" |
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/Recommendations-for-Data-Repositories" |
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:24:08 GMT" |
expires | "Tue, 01 Jan 1980 00:00:00 GMT" |
pragma | "no-cache" |
x-debug-token | "4e41e6" |
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_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/Recommendations-for-Data-Repositories" |
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 | "61531" |
REQUEST_METHOD | "GET" |
REQUEST_SCHEME | "https" |
REQUEST_TIME | 1738826648 |
REQUEST_TIME_FLOAT | 1738826648.2431 |
REQUEST_URI | "/Recommendations-for-Journals-and-Publishers" |
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" |