{"id":3614,"date":"2025-12-12T11:46:41","date_gmt":"2025-12-12T09:46:41","guid":{"rendered":"https:\/\/dataverse.lv\/?page_id=3614"},"modified":"2025-12-12T12:05:04","modified_gmt":"2025-12-12T10:05:04","slug":"dataverselv-digital-preservation-policy","status":"publish","type":"page","link":"https:\/\/dataverse.lv\/en\/dataverselv-digital-preservation-policy\/","title":{"rendered":"DataverseLV Digital Preservation Policy"},"content":{"rendered":"

DataverseLV<\/span>\u00a0Digital Preservation Policy<\/span><\/h1>\n<\/div>

1. Policy purpose and scope<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
DataverseLV is Latvia\u2019s national research data repository, providing long-term preservation, access, and reuse of datasets created by the research community. DataverseLV Digital Preservation Policy (hereinafter, the Policy) sets out the repository\u2019s commitment and approach to the responsible and sustainable long-term storage, accessibility, and usability of research data. The Policy is developed in accordance with the Latvian Open Science Strategy, the OAIS reference model, the TRUST principles, the FAIR data principles, and the CoreTrustSeal requirements. The Policy applies to all datasets and their metadata published in DataverseLV, as well as to the processes from ingest to deaccessioning in the repository. The intended audience of the Policy includes dataset depositors, data curators, repository administrators, the LVRTC infrastructure operator, and the general DataverseLV user community.<\/h5>\n<\/div>

Definitions of terms used in the Policy<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>

Hosting<\/strong> \u2014 deployment and maintenance of applications and services on server infrastructure (OS, application server, database, network) that ensures DataverseLV operation.\u200b<\/p>\n

Data storage<\/strong> \u2014 secure preservation of digital data in storage systems with replication, backups, and availability restoration in accordance with the SLA.\u200b<\/p>\n

OAIS (ISO 14721)<\/strong> \u2014 an international reference model for an Open Archival Information System for long-term preservation and access, defining functions, processes, and terminology.\u200b<\/p>\n

TRUST principles<\/strong> \u2014 guidelines for ensuring trustworthy repositories: Transparency, Responsibility, User focus, Sustainability, Technology.\u200b<\/p>\n

Fixity (integrity check)<\/strong> \u2014 evidence that a file has not changed at the bit level; the originally recorded and re-calculated checksums are compared.\u200b<\/p>\n

DOI<\/strong> \u2014 a persistent digital identifier for datasets and their versions that ensures durable citation and findability.\u200b<\/p>\n

Deaccessioning (withdrawal)<\/strong> \u2014 the removal of published data or parts thereof in exceptional cases; the DOI and metadata remain with a tombstone record explaining the reason.\u200b<\/p>\n

Embargo<\/strong> \u2014 a period during which data are not publicly available, after which access is opened according to the rules.\u200b<\/p>\n

Bit-level preservation<\/strong> \u2014 preservation focused on bit integrity (checksums, replication, backups) without engaging in content transformation.\u200b<\/p>\n

Normalization<\/strong> \u2014 conversion of files to recommended, preservation-friendly formats to mitigate risk and obsolescence.\u200b<\/p>\n

Format<\/strong> migration<\/strong> \u2014 planned transfer from an obsolete format to a current one while preserving essential characteristics and usability.\u200b<\/p>\n

SLA<\/strong> \u2014 a service-level agreement on availability, incident reporting\/remediation, and recovery objectives between VPC and LVRTC.\u200b<\/p>\n

RTO\/RPO<\/strong> \u2014 recovery time objective and recovery point objective.\u200b<\/p>\n

Curator<\/strong> \u2014 a repository specialist who helps depositors prepare data\/metadata, checking compliance and quality before publication.\u200b<\/p>\n

OAI-PMH<\/strong> \u2014 a standard protocol that allows external systems to harvest and index metadata from the repository.<\/p>\n

API<\/strong> – a set of technical protocols that allows other software and systems to automate tasks such as uploading data or searching the repository without using the website interface.<\/p>\n<\/div>

2. Organizational responsibility and governance<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
The operation of the repository is ensured by The Higher Education and Science\u202fInformation Technology\u202fShared Service Centre (VPC), which is the central administrative structure for the management, processes and software administration of the repository. The physical infrastructure and hosting of the repository is ensured by the Latvian State Radio and Television Centre (LVRTC) as the operator of the national critical infrastructure in accordance with the mutual SLA. Partner universities manage their institutional collections and provide data curators for data preparation and quality monitoring; the supervision of the rest of the institutional collections is provided by the data curators of the VPC.<\/h5>\n<\/div>

2.1. DataverseLV<\/span>\u00a0<\/span>roles<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>

Depositor<\/strong>: ensures dataset usage rights, ethical and legal compliance, use of recommended formats, and complete documentation when submitting data for publication.<\/p>\n

Partner institution curators<\/strong>: verify the quality and compliance of datasets from their institution, advise on metadata, licenses, formats, and access, and coordinate publication.<\/p>\n

VPC data curators<\/strong>: oversee institutional collections not managed by partner universities, ensuring consistent quality practices across the repository.<\/p>\n

Repository administrators (VPC)<\/strong>: maintain DataverseLV software, access permissions, version control, and process documentation.<\/p>\n

LVRTC<\/strong>: provides repository hosting and data storage with replication and backups, in compliance with SLA and Cabinet of Ministers Instruction No. 5.<\/p>\n

VPC board<\/strong>: approves the policy and strategic decisions, ensuring continuity of governance.<\/p>\n<\/div>

3. OAIS compliance and functions<\/span><\/span><\/h4>\n<\/div>
DataverseLV preservation processes are aligned with the OAIS model and encompass pre-ingest, ingest, archival storage, data management, access, administration, and preservation planning.<\/h5>\n
During pre-ingest<\/strong>, the repository provides guidelines, training, and lists of recommended file formats for depositors.<\/h5>\n
During ingest<\/strong>, data integrity and completeness are checked, metadata are validated, MD5 checksums are generated, and data quality is reviewed prior to publication.<\/h5>\n
In archival storage<\/strong>, replication and backups are implemented across two geographically separated locations.<\/h5>\n
In data management<\/strong>, administrative, descriptive, and access metadata are maintained, along with version history with unique DOIs.<\/h5>\n
Access<\/strong> is provided via a web interface, OAI-PMH, and API with flexible access control.<\/h5>\n
Administration<\/strong> functions are shared between VPC and partners with clear roles and responsibilities.<\/h5>\n<\/div>

3.1.\u00a0Implementation<\/span>\u00a0<\/span>of<\/span>\u00a0<\/span>the<\/span>\u00a0TRUST\u00a0<\/span>principles<\/span><\/span><\/h4>\n<\/div>
DataverseLV implements transparency, accountability, user focus, sustainability, and the use of secure, modern technology across the entire data lifecycle.\u200b
\nAspects of policies, procedures, and SLA covering availability, incidents, and recovery are documented and communicated to stakeholders.\u200b
\nSustainability is ensured through stable governance, funding, and critical infrastructure services.\u200b<\/h5>\n<\/div>

4. Preservation strategy<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
The goal is to ensure long-term accessibility and usability by accepting and storing data in formats that are documented, widely supported, and suitable for preservation.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

4.1. Format policy<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
The repository accepts only recommended, preservation-suitable file formats<\/a> for deposit; if data are in another format, the depositor must convert them before publication with curator support.\u200b
\nThe list of recommended formats and guidance is available in the dataverse.lv guide, and curators help assess compliance prior to publication.\u200b<\/h5>\n<\/div>

4.2. Acceptance and integrity<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
At the point of ingest, checksums are calculated and recorded for all files to enable bit-level integrity verification in\u00a0<\/span>subsequent<\/span>\u00a0stages.<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

4.3. Storage and access<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
Data and metadata are stored on secure national infrastructure with replication across two geographically separated locations and regular backups\u00a0<\/span>in accordance with<\/span>\u00a0the SLA.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span>
<\/span>Availability, recovery\u00a0<\/span>objectives<\/span>\u00a0(RTO\/RPO), and incident processes are defined in the VPC\u2013LVRTC SLA and are periodically tested.<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

4.4. Changes and versions<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
Any change to the data or documentation results in a new dataset version with a unique DOI and a complete change history, preserving\u00a0<\/span>citability<\/span>.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span>
<\/span>Also\u00a0<\/span>corrections are recorded separately<\/span>\u00a0in the quality checklist and stored in internal VPC Documentation<\/span>, and\u00a0<\/span>previous<\/span>\u00a0versions\u00a0<\/span>remain<\/span>\u00a0accessible for audit purposes.<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

4.5. Format obsolescence<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
The repository does not perform centralized post-publication data improvement or general format migration; the responsibility for using recommended formats lies with the depositor, with curator support during the preparation stage.<\/span>\u00a0<\/span><\/h5>\n
If a risk of format obsolescence is\u00a0identified, the repository advises the depositor on potential republication in a recommended format and ensures\u00a0version\u00a0continuity.<\/span>\u00a0<\/span><\/h5>\n<\/div>

4.6. Exceptions and support<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
In exceptional cases where applying the recommended format is not practically possible, a curator assessment is performed and an alternative is agreed with clear documentation of the choice in the quality checklist.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span>
<\/span>In all cases, preference is given to open, well-documented, and community-supported formats to minimize dependencies and future migration risks.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

5. Dataset<\/span>\u00a0ingest\u202fand description<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
Ingest criteria include checks for rights compliance, protection or anonymization of sensitive information, adherence to legal requirements, and absence of malware.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span>
<\/span>During ingest, integrity checks, MD5 checksum generation, completeness verification, and, if needed, format identification are performed.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span>
<\/span>International standards are used for metadata description to ensure findability and interoperability.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

5.1. FAIR principles support<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
DataverseLV\u00a0implements FAIR (Findable, Accessible, Interoperable, Reusable) principles to ensure that research data are findable, accessible, interoperable, and reusable for both humans and machine-readable processes:<\/span>\u200b<\/span>\u00a0<\/span><\/h5>\n
Findable: Each dataset is\u00a0assigned\u00a0a unique, persistent DOI for precise citation and discoverability in search engines. Datasets are described with rich metadata using international standards and are indexed in discovery systems, enabling users to find data by multiple criteria.<\/span>\u200b<\/span>\u00a0<\/span><\/h5>\n
Accessible: Datasets and their metadata are available through clearly defined access protocols\u2014the web interface, OAI-PMH, and REST API. Even when files are access-restricted, metadata\u00a0remain\u00a0open,\u00a0indicating\u00a0the data's existence and access conditions. Access rights and licenses are clearly\u00a0stated.<\/span>\u200b<\/span>\u00a0<\/span><\/h5>\n
Interoperable: The repository supports open metadata standards (e.g., Dublin Core,\u00a0DataCite) for system-to-system compatibility and integration across contexts. The OAI-PMH protocol and APIs enable automated harvesting and integration with other research infrastructures. Using recommended file formats ensures technical compatibility.<\/span>\u200b<\/span>\u00a0<\/span><\/h5>\n
Reusable: Datasets include sufficient documentation (ReadMe\u00a0files, codebooks, methodological descriptions), clear\u00a0use\u00a0licenses, and version history, enabling others to reuse the data in\u00a0new studies. A versioning policy\u00a0maintains\u00a0a transparent, citable change record to support research reproducibility and traceability.<\/span>\u200b<\/span>\u00a0<\/span><\/h5>\n<\/div>

5.2. Draft dataset management<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
Drafts are operational records maintained only until publication or deletion per the depositor's preferences; long-term preservation applies to published datasets and metadata.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span>
<\/span>Drafts may be deleted by the depositor or a curator if they do not meet requirements or are not progressing toward publication, and all actions are recorded in quality control logs.<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

6. Version control and change management<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
Minor versions apply to metadata corrections or additions, while major versions include changes to data or documentation files.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span>Each version has a unique DOI, with a complete version history preserved and access to\u00a0<\/span>previous<\/span>\u00a0versions\u00a0<\/span>maintained<\/span>.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span>Users can cite a specific version or always the latest version, depending on need.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

7. Dat<\/span>aset\u00a0<\/span>deaccessioning<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
Deaccessioning is permitted in cases of legal or ethical violations, copyright disputes, a substantiated depositor request, or irreversible loss of integrity.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span>
<\/span>Files are deleted while retaining the DOI and metadata via a tombstone record that states the reason for deaccessioning.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span>
<\/span>All deaccessioning cases are recorded in the dataset's quality control checklist for governance and compliance purposes.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

8. Infrastructure<\/span>,\u00a0<\/span>SLA<\/span>\u00a0<\/span>and<\/span>\u00a0<\/span>security<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
Data and metadata are stored on LVRTC infrastructure with synchronous replication across two geographically separate sites and daily, weekly, and monthly backups.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span>
<\/span>Availability, incident reporting, recovery procedures, RTO, and RPO are defined in the VPC\u2013LVRTC SLAs and are regularly tested\u00a0<\/span>in accordance with<\/span>\u00a0the agreeme<\/span>nt<\/span><\/span>\u200b<\/span>.<\/span><\/span>\u00a0<\/span>
<\/span>The infrastructure is\u00a0<\/span>maintained<\/span>\u00a0in line with information security standards and national regulations.<\/span><\/span>\u200b<\/span><\/span>\u00a0<\/span>
<\/span>The LVRTC\u00a0<\/span>SLA<\/span>\u00a0is developed and applied\u00a0<\/span>in accordance with<\/span>\u00a0<\/span><\/span>Cabinet Instruction No. 5 of 8 November 2022 \"Procedure for ensuring the State Electronic Communications Service Centre.\"<\/span><\/span>\u200b<\/span><\/span><\/a>\u00a0<\/span><\/h5>\n<\/div>

8.1. Information security and access control\u202f<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
Secure authentication, role-based access control, firewalls, encrypted data transfer, and auditing are used. Administrative access is strictly\u00a0<\/span>limited<\/span>\u00a0and emergency access is only possible in defined cases under the SLA. Compliance with data protection requirements is ensured according to defined roles and processes.<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

9. Risk assessment and incident management<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
Risk identification, assessment,\u00a0monitoring\u00a0and documentation\u00a0is\u00a0implemented\u00a0in accordance with\u00a0the VPC and LVRTC cooperation model,\u00a0observing\u00a0the LVRTC Service Level Agreement (SLA), which is based on Cabinet Instruction No. 5 of 8 November 2022.\u00a0Availability\u00a0indicators, incident reporting channels, response times, escalation\u00a0procedures\u00a0and reports are defined in the LVRTC SLA, and the operational coordination of these processes is provided by the VPC.<\/span>\u00a0<\/span><\/h5>\n
Fixity checks<\/span><\/b>\u00a0and other bit-level integrity audits are internal processes and tools in\u00a0DataverseLV\u00a0that work independently of SLA and provide data immutability monitoring.<\/span>\u00a0<\/span><\/h5>\n
Backup restoration testing and event logging are performed periodically according to a defined schedule to verify RTO\/RPO reach and process readiness. If integrity discrepancies or other incidents are detected, the data is restored from the last secure copy by applying the incident and recovery procedures set out in the SLA in the coordination of the VPC.<\/span>\u00a0<\/span><\/h5>\n<\/div>

10.\u00a0<\/span>Succession and continuity<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
Continuity is ensured by LVRTC as a national critical infrastructure operator, with\u00a0DataverseLV\u00a0operating on secure, geographically backed up infrastructure with backups and monitoring. Changes to the hosting of the repository are not planned, and service availability, incident reporting procedures, response\u00a0times\u00a0and recovery targets (RTO\/RPO) are implemented\u00a0in accordance with\u00a0the LVRTC SLA, which is operationally coordinated by the VPC.<\/span>\u00a0<\/span><\/h5>\n
In the event of\u00a0critical disruptions, the incident and restoration procedures\u00a0established\u00a0by the SLA are applied until the service is fully restored to the same infrastructure, with users informed about the status and progress of operations. DOI and metadata are\u00a0maintained\u00a0unchanged, ensuring\u00a0citability\u00a0and findability of information even during incidents,\u00a0<\/span>while for planned or unplanned work, a temporary access restriction (e.g.\u00a0read-only mode) may be applied with prior notice when possible.<\/span><\/b>\u00a0<\/span><\/h5>\n<\/div>

11. \u00a0<\/span>Retention periods and availability<\/span><\/span><\/span><\/h4>\n<\/div>
Published data is\u00a0<\/span>retained<\/span>\u00a0without a time limit<\/span>\u00a0T<\/span>he<\/span>\u00a0DOI identifier is also\u00a0<\/span>maintained<\/span>\u00a0<\/span>in the event of<\/span>\u00a0deletion, and a publicly available \"tombstone\" entry explains the reason for the removal and\u00a0<\/span>retains\u00a0<\/span>citability<\/span>. Access to datasets is\u00a0<\/span>determined<\/span>\u00a0according to usage needs, supporting\u00a0<\/span>open access<\/span>, restricted\u00a0<\/span>access<\/span>\u00a0and embargo periods.<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

12. Financial sustainability<\/span><\/span><\/span><\/span><\/h4>\n<\/div>
The creation of\u00a0<\/span>DataverseLV<\/span>\u00a0has been implemented within the framework of the project \"Support for the implementation of open science in practice, as well as solutions for sharing science data and participation in the EU open science cloud\" (RRF project No. 2.1.3.1.i) with financial support from the European Union Recovery Fund and the State of Latvia. Further maintenance shall be ensured by the partner funding model and the national reference funding for open science initiatives, with an operational horizon of at least five years and a regular budget review. The aim is to ensure the continuity of staff, repository\u00a0<\/span>hosting<\/span>\u00a0and platform development by providing scenarios for different funding conditions.<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

13.\u00a0<\/span>Technical platform and standards<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
DataverseLV<\/span>\u00a0uses the open source Dataverse platform with regular updates and support from the international community. The technical environment includes Linux, Payara, PostgreSQL,\u00a0<\/span>Solr<\/span>\u00a0and\u00a0<\/span>additional<\/span>\u00a0tools for monitoring activity. Supported OAI-PMH, REST API and DOI registration, as well as data and metadata export capabilities.<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

14.\u00a0<\/span>Policy review and update<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
The policy shall be reviewed at least every three years or sooner in the event of changes in technology, legal framework or international standards.<\/span>\u00a0Changes are documented,\u00a0<\/span>co-ordinated<\/span>, and made public,\u00a0<\/span>maintaining<\/span>\u00a0a public\u00a0<\/span>version<\/span>\u00a0history and ensuring transparency. The current version is published on the\u00a0<\/span>DataverseLV<\/span>\u00a0website.<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

15.\u00a0<\/span>Community involvement and support<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
User needs are\u00a0<\/span>identified<\/span>\u00a0through curatorial support, working groups, consultations, and guidelines, including recommended format and quality checklists. International collaborations with the Dataverse community and European infrastructures ensure alignment with best practices. Feedback is systematically used in the improvement of processes and services.<\/span><\/span>\u00a0<\/span><\/h5>\n<\/div>

1<\/span>6. Contacts<\/span><\/span>\u00a0<\/span><\/h4>\n<\/div>
Email:\u00a0<\/span>info@vpc.lv<\/span><\/a>
\nPhone: +371 67 969 580<\/span>
\nAddress:\u00a0Zigfr\u012bda\u00a0Annas\u00a0Meierovica\u00a0bulv\u0101ris\u00a014,\u00a0R\u012bga, LV-1050, Latvia<\/span>
\nWebsite:\u00a0<\/span>https:\/\/dataverse.lv\/<\/span><\/a>\u00a0<\/span><\/h5>\n<\/div><\/div><\/div><\/div><\/div>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_price":"","_stock":"","_tribe_ticket_header":"","_tribe_default_ticket_provider":"","_tribe_ticket_capacity":"0","_ticket_start_date":"","_ticket_end_date":"","_tribe_ticket_show_description":"","_tribe_ticket_show_not_going":false,"_tribe_ticket_use_global_stock":"","_tribe_ticket_global_stock_level":"","_global_stock_mode":"","_global_stock_cap":"","_tribe_rsvp_for_event":"","_tribe_ticket_going_count":"","_tribe_ticket_not_going_count":"","_tribe_tickets_list":"[]","_tribe_ticket_has_attendee_info_fields":false,"footnotes":"","_tec_slr_enabled":"","_tec_slr_layout":""},"class_list":["post-3614","page","type-page","status-publish","hentry"],"ticketed":false,"_links":{"self":[{"href":"https:\/\/dataverse.lv\/en\/wp-json\/wp\/v2\/pages\/3614","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dataverse.lv\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/dataverse.lv\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/dataverse.lv\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/dataverse.lv\/en\/wp-json\/wp\/v2\/comments?post=3614"}],"version-history":[{"count":5,"href":"https:\/\/dataverse.lv\/en\/wp-json\/wp\/v2\/pages\/3614\/revisions"}],"predecessor-version":[{"id":3619,"href":"https:\/\/dataverse.lv\/en\/wp-json\/wp\/v2\/pages\/3614\/revisions\/3619"}],"wp:attachment":[{"href":"https:\/\/dataverse.lv\/en\/wp-json\/wp\/v2\/media?parent=3614"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}