diff --git a/.gitignore b/.gitignore index 1e802991547..624691049bc 100644 --- a/.gitignore +++ b/.gitignore @@ -2,6 +2,9 @@ nb-configuration.xml target infer-out nbactions.xml +.settings +.classpath +.project michael-local GPATH GTAGS diff --git a/doc/sphinx-guides/source/admin/metadataexport.rst b/doc/sphinx-guides/source/admin/metadataexport.rst index 27df2d4e7a3..078177b609a 100644 --- a/doc/sphinx-guides/source/admin/metadataexport.rst +++ b/doc/sphinx-guides/source/admin/metadataexport.rst @@ -7,14 +7,7 @@ Metadata Export Automatic Exports ----------------- -Publishing a dataset automatically starts a metadata export job, that will run in the background, asynchronously. Once completed, it will make the dataset metadata exported and cached in all the supported formats: - -- Dublin Core -- Data Documentation Initiative (DDI) -- DataCite 4 -- native JSON (Dataverse-specific) -- OAI_ORE -- Schema.org JSON-LD +Publishing a dataset automatically starts a metadata export job, that will run in the background, asynchronously. Once completed, it will make the dataset metadata exported and cached in all the supported formats listed under :ref:`Supported Metadata Export Formats ` in the :doc:`/user/dataset-management` section of the User Guide. A scheduled timer job that runs nightly will attempt to export any published datasets that for whatever reason haven't been exported yet. This timer is activated automatically on the deployment, or restart, of the application. So, again, no need to start or configure it manually. (See the "Application Timers" section of this guide for more information) diff --git a/doc/sphinx-guides/source/api/native-api.rst b/doc/sphinx-guides/source/api/native-api.rst index edec1ca2625..c0d1bfd8e11 100644 --- a/doc/sphinx-guides/source/api/native-api.rst +++ b/doc/sphinx-guides/source/api/native-api.rst @@ -291,7 +291,7 @@ Export Metadata of a Dataset in Various Formats GET http://$SERVER/api/datasets/export?exporter=ddi&persistentId=$persistentId -.. note:: Supported exporters (export formats) are ``ddi``, ``oai_ddi``, ``dcterms``, ``oai_dc``, ``schema.org`` , ``OAI_ORE`` , ``Datacite`` and ``dataverse_json``. +.. note:: Supported exporters (export formats) are ``ddi``, ``oai_ddi``, ``dcterms``, ``oai_dc``, ``schema.org`` , ``OAI_ORE`` , ``Datacite``, ``oai_datacite`` and ``dataverse_json``. Schema.org JSON-LD ^^^^^^^^^^^^^^^^^^ diff --git a/doc/sphinx-guides/source/user/dataset-management.rst b/doc/sphinx-guides/source/user/dataset-management.rst index 835594b3410..c2b272725dd 100755 --- a/doc/sphinx-guides/source/user/dataset-management.rst +++ b/doc/sphinx-guides/source/user/dataset-management.rst @@ -20,7 +20,20 @@ A dataset contains three levels of metadata: For more details about what Citation and Domain Specific Metadata is supported please see our :ref:`user-appendix`. -Note that once a dataset has been published its metadata may be exported. A button on the dataset page's metadata tab will allow a user to export the metadata of the most recently published version of the dataset. Currently supported export formats are DDI, Dublin Core, Datacite 4, OAI_ORE, Schema.org JSON-LD, and Dataverse's native JSON format. +.. _metadata-export-formats: + +Supported Metadata Export Formats +--------------------------------- + +Once a dataset has been published its metadata is exported in a variety of formats. A button on the dataset page's metadata tab will allow a user to export the metadata of the most recently published version of the dataset. Currently supported export formats are: + +- Dublin Core +- DDI (Data Documentation Initiative) +- DataCite 4 +- JSON (native Dataverse format) +- OAI_ORE +- OpenAIRE +- Schema.org JSON-LD Adding a New Dataset ==================== @@ -510,4 +523,4 @@ If you deaccession the most recently published version of the dataset but not al .. |file-upload-prov-window| image:: ./img/prov1.png :class: img-responsive .. |image-file-tree-view| image:: ./img/file-tree-view.png - :class: img-responsive \ No newline at end of file + :class: img-responsive diff --git a/pom.xml b/pom.xml index 75cb754f9d1..fcc0deb0658 100644 --- a/pom.xml +++ b/pom.xml @@ -599,6 +599,12 @@ tika-parsers 1.19 + + + org.apache.opennlp + opennlp-tools + 1.9.1 +