, ,
, , , , , , ).
* **Category**: Select a category that best describes the type of dataverse this will be. For example, if this is a dataverse for an individual researcher's datasets, select Researcher. If this is a dataverse for an institution, select Organization & Institution.
- * **Choose the sets of Metadata Elements for datasets in this dataverse**: by default the metadata elements will be from the host dataverse that this new dataverse is created in. Dataverse offers metadata standards for multiple domains. To learn more about the metadata standards in Dataverse please check out the :doc:`/user/appendix`.
+ * **Choose the sets of Metadata Elements for datasets in this dataverse**: By default the metadata elements will be from the host dataverse that this new dataverse is created in. Dataverse offers metadata standards for multiple domains. To learn more about the metadata standards in Dataverse please check out the :doc:`/user/appendix`.
* **Select facets for this dataverse**: by default the facets that will appear on your dataverse landing page will be from the host dataverse that this new dataverse was created in. The facets are simply metadata fields that can be used to help others easily find dataverses and datasets within this dataverse. You can select as many facets as you would like.
#. Selected metadata elements are also used to pick which metadata fields you would like to use for creating templates for your datasets. Metadata fields can be hidden, or selected as required or optional. Once you have selected all the fields you would like to use, you can create your template(s) after you finish creating your dataverse.
#. Click "Create Dataverse" button and you're done!
@@ -51,7 +54,7 @@ General Information
The General Information page is how you edit the information you filled in while creating your dataverse. If you need to change or add a contact email address, this is the place to do it. Additionally, you can update the metadata elements used for datasets within the dataverse, change which metadata fields are hidden, required, or optional, and update the facets you would like displayed for browsing the dataverse. If you plan on using templates, you need to select the metadata fields on the General Information page.
-Tip: The metadata fields you select as required, will appear on the Create Dataset form when someone goes to add a dataset to the dataverse.
+Tip: The metadata fields you select as required will appear on the Create Dataset form when someone goes to add a dataset to the dataverse.
.. _theme:
@@ -115,7 +118,7 @@ You can also give access to a Dataverse user to allow them to access an unpublis
Dataset Templates
======================
-Templates are useful when you have several datasets that have the same information in multiple metadata fields that you would prefer not to have to keep manually typing in or want to use a custom set of Terms of Use and Access for multiple datasets in a dataverse. In Dataverse 4.0, templates are created at the dataverse level, can be deleted (so it does not show for future datasets), set to default (not required), or can be copied so you do not have to start over when creating a new template with similiar metadata from another template. When a template is deleted, it does not impact the datasets that have used the template already.
+Templates are useful when you have several datasets that have the same information in multiple metadata fields that you would prefer not to have to keep manually typing in, or if you want to use a custom set of Terms of Use and Access for multiple datasets in a dataverse. In Dataverse 4.0, templates are created at the dataverse level, can be deleted (so it does not show for future datasets), set to default (not required), or can be copied so you do not have to start over when creating a new template with similiar metadata from another template. When a template is deleted, it does not impact the datasets that have used the template already.
How do you create a template?
diff --git a/doc/sphinx-guides/source/user/find-use-data.rst b/doc/sphinx-guides/source/user/find-use-data.rst
index 5395593a2ad..f62877a32fc 100755
--- a/doc/sphinx-guides/source/user/find-use-data.rst
+++ b/doc/sphinx-guides/source/user/find-use-data.rst
@@ -1,6 +1,9 @@
Finding and Using Data
+++++++++++++++++++++++
+.. contents:: |toctitle|
+ :local:
+
Finding Data
=============
diff --git a/doc/sphinx-guides/source/user/index.rst b/doc/sphinx-guides/source/user/index.rst
index 9d231cb5f6d..05973e6fac9 100755
--- a/doc/sphinx-guides/source/user/index.rst
+++ b/doc/sphinx-guides/source/user/index.rst
@@ -6,7 +6,7 @@
User Guide
=================================================
-Contents:
+**Contents:**
.. toctree::
diff --git a/doc/sphinx-guides/source/user/tabulardataingest/csv.rst b/doc/sphinx-guides/source/user/tabulardataingest/csv.rst
index 87369471567..f716a6d4428 100644
--- a/doc/sphinx-guides/source/user/tabulardataingest/csv.rst
+++ b/doc/sphinx-guides/source/user/tabulardataingest/csv.rst
@@ -1,6 +1,9 @@
CSV
++++++
+.. contents:: |toctitle|
+ :local:
+
Ingest of Comma-Separated Values files as tabular data.
-------------------------------------------------------
@@ -9,7 +12,7 @@ Dataverse will make an attempt to turn CSV files uploaded by the user into tabul
Main formatting requirements:
-----------------------------
-The first line must contan a comma-separated list of the variable names;
+The first line must contain a comma-separated list of the variable names;
All the lines that follow must contain the same number of comma-separated values as the first, variable name line.
diff --git a/doc/sphinx-guides/source/user/tabulardataingest/excel.rst b/doc/sphinx-guides/source/user/tabulardataingest/excel.rst
index ea51cda1870..b8612092f06 100644
--- a/doc/sphinx-guides/source/user/tabulardataingest/excel.rst
+++ b/doc/sphinx-guides/source/user/tabulardataingest/excel.rst
@@ -1,6 +1,9 @@
Excel
+++++++
+.. contents:: |toctitle|
+ :local:
+
Excel files (**New** in Dataverse 4.0!)
Note: only the "new", XLSX Excel files are supported. We are not planning to add support for the old-style, binary XLS files.
diff --git a/doc/sphinx-guides/source/user/tabulardataingest/ingestprocess.rst b/doc/sphinx-guides/source/user/tabulardataingest/ingestprocess.rst
index 12ae430bd67..4f71dd9944f 100644
--- a/doc/sphinx-guides/source/user/tabulardataingest/ingestprocess.rst
+++ b/doc/sphinx-guides/source/user/tabulardataingest/ingestprocess.rst
@@ -6,6 +6,8 @@ the application and what happens during the ingest process, as the
files uploaded by the user are processed and converted into the
archival format in the Dataverse application.
+.. contents:: |toctitle|
+ :local:
What Happens During this "Ingest"?
===================================
diff --git a/doc/sphinx-guides/source/user/tabulardataingest/rdata.rst b/doc/sphinx-guides/source/user/tabulardataingest/rdata.rst
index ae2cc6cf7fe..0707051b5a2 100644
--- a/doc/sphinx-guides/source/user/tabulardataingest/rdata.rst
+++ b/doc/sphinx-guides/source/user/tabulardataingest/rdata.rst
@@ -3,6 +3,8 @@ R Data Format
Support for R (.RData) files has been introduced in DVN 3.5.
+.. contents:: |toctitle|
+ :local:
Overview.
===========
diff --git a/doc/sphinx-guides/source/user/tabulardataingest/spss.rst b/doc/sphinx-guides/source/user/tabulardataingest/spss.rst
index 86a7d864851..71bc61265c3 100644
--- a/doc/sphinx-guides/source/user/tabulardataingest/spss.rst
+++ b/doc/sphinx-guides/source/user/tabulardataingest/spss.rst
@@ -3,6 +3,9 @@ SPSS
SPSS data files (POR and SAV formats).
+.. contents:: |toctitle|
+ :local:
+
Supported Versions
------------------
diff --git a/doc/sphinx-guides/source/user/tabulardataingest/stata.rst b/doc/sphinx-guides/source/user/tabulardataingest/stata.rst
index 764bc815a2f..e17e7321eae 100644
--- a/doc/sphinx-guides/source/user/tabulardataingest/stata.rst
+++ b/doc/sphinx-guides/source/user/tabulardataingest/stata.rst
@@ -1,6 +1,9 @@
Stata
++++++++
+.. contents:: |toctitle|
+ :local:
+
Of all the third party statistical software providers, Stata does the best job at documenting the internal format of their files, by far. And at making that documentation freely and easily available to developers (yes, we are looking at you, SPSS). Because of that, Stata is the best supported format for tabular data ingest.
diff --git a/doc/sphinx-guides/source/user/tabulardataingest/supportedformats.rst b/doc/sphinx-guides/source/user/tabulardataingest/supportedformats.rst
index b5104a5a2c0..6078d37ee84 100644
--- a/doc/sphinx-guides/source/user/tabulardataingest/supportedformats.rst
+++ b/doc/sphinx-guides/source/user/tabulardataingest/supportedformats.rst
@@ -1,8 +1,11 @@
Supported File Formats
+++++++++++++++++++++++++++++
+.. contents:: |toctitle|
+ :local:
+
Tabular Data ingest supports the following file formats:
-(see the sections below for more information on each of the supported formats)
+
================================ ==================================
File format Versions supported
@@ -13,3 +16,5 @@ R up to 3
Excel XLSX only (XLS is NOT supported)
CSV (comma-separated values) (limited support)
================================ ==================================
+
+See the subsections in the left sidebar for more information on each of these supported formats.
\ No newline at end of file
diff --git a/pom.xml b/pom.xml
index 98ea5a047ad..ba4886dda60 100644
--- a/pom.xml
+++ b/pom.xml
@@ -4,7 +4,7 @@
edu.harvard.iq
dataverse
- 4.6.2
+ 4.7
war
dataverse
diff --git a/scripts/api/setup-optional-harvard.sh b/scripts/api/setup-optional-harvard.sh
index 4bcae4c8685..c1815998e6e 100755
--- a/scripts/api/setup-optional-harvard.sh
+++ b/scripts/api/setup-optional-harvard.sh
@@ -21,7 +21,7 @@ echo "- Enabling Geoconnect"
curl -s -X PUT -d true "$SERVER/admin/settings/:GeoconnectCreateEditMaps"
curl -s -X PUT -d true "$SERVER/admin/settings/:GeoconnectViewMaps"
echo "- Setting system email"
-curl -X PUT -d "Dataverse Support " http://localhost:8080/api/admin/settings/:SystemEmail
+curl -X PUT -d "Harvard Dataverse Support " http://localhost:8080/api/admin/settings/:SystemEmail
curl -X PUT -d ", The President & Fellows of Harvard College" http://localhost:8080/api/admin/settings/:FooterCopyright
echo "- Setting up the Harvard Shibboleth institutional group"
curl -s -X POST -H 'Content-type:application/json' --upload-file data/shibGroupHarvard.json "$SERVER/admin/groups/shib?key=$adminKey"
diff --git a/scripts/database/upgrades/upgrade_v4.6.2_to_v4.7.sql b/scripts/database/upgrades/upgrade_v4.6.2_to_v4.7.sql
new file mode 100644
index 00000000000..901b013a104
--- /dev/null
+++ b/scripts/database/upgrades/upgrade_v4.6.2_to_v4.7.sql
@@ -0,0 +1,2 @@
+--Uncomment to preserve "Dataverse" at end of each dataverse name.
+--UPDATE dataverse SET name = name || ' Dataverse';
diff --git a/src/main/java/Bundle.properties b/src/main/java/Bundle.properties
index 5c3fd33a754..ab8e29b663b 100755
--- a/src/main/java/Bundle.properties
+++ b/src/main/java/Bundle.properties
@@ -90,11 +90,6 @@ body.skip=Skip to main content
# dataverse_footer.xhtml
-footer.codeAvailable=Code available at
-footer.dataverseOnGitHub=Dataverse On GitHub
-footer.dataverseProjectOn=Dataverse Project on
-footer.Twitter=Twitter
-footer.dataScienceIQSS=Developed at the Institute for Quantitative Social Science
footer.copyright=Copyright © {0}
footer.widget.datastored=Data is stored at {0}.
footer.widget.login=Log in to
@@ -112,11 +107,11 @@ messages.validation.msg=Required fields were missed or there was a validation er
# contactFormFragment.xhtml
-contact.header=Contact Dataverse Support
+contact.header=Contact {0}
contact.dataverse.header=Email Dataverse Contact
contact.dataset.header=Email Dataset Contact
contact.to=To
-contact.support=Dataverse Support
+contact.support=Support
contact.from=From
contact.from.required=User email is required.
contact.from.invalid=Email is invalid.
@@ -154,7 +149,7 @@ wasReturnedByReviewer=, was returned by the curator of
toReview=Don't forget to publish it or send it back to the contributor!
worldMap.added=dataset had a WorldMap layer data added to it.
# Bundle file editors, please note that "notification.welcome" is used in a unit test.
-notification.welcome=Welcome to {0} Dataverse! Get started by adding or finding data. Have questions? Check out the {1}. Want to test out Dataverse features? Use our {2}. Also, check for your welcome email to verify your address.
+notification.welcome=Welcome to {0}! Get started by adding or finding data. Have questions? Check out the {1}. Want to test out Dataverse features? Use our {2}. Also, check for your welcome email to verify your address.
notification.demoSite=Demo Site
notification.requestFileAccess=File access requested for dataset: {0}.
notification.grantFileAccess=Access granted for files in dataset: {0}.
@@ -498,38 +493,38 @@ harvestserver.viewEditDialog.btn.save=Save Changes
#MailServiceBean.java
-notification.email.create.dataverse.subject=Dataverse: Your dataverse has been created
-notification.email.create.dataset.subject=Dataverse: Your dataset has been created
-notification.email.request.file.access.subject=Dataverse: Access has been requested for a restricted file
-notification.email.grant.file.access.subject=Dataverse: You have been granted access to restricted file
-notification.email.rejected.file.access.subject=Dataverse: Your request for access to restricted file has been rejected
-notification.email.update.maplayer=Dataverse: WorldMap layer added to dataset
-notification.email.maplayer.deletefailed.subject=Failed to delete WorldMap layer
+notification.email.create.dataverse.subject={0}: Your dataverse has been created
+notification.email.create.dataset.subject={0}: Your dataset has been created
+notification.email.request.file.access.subject={0}: Access has been requested for a restricted file
+notification.email.grant.file.access.subject={0}: You have been granted access to a restricted file
+notification.email.rejected.file.access.subject={0}: Your request for access to a restricted file has been rejected
+notification.email.update.maplayer={0}: WorldMap layer added to dataset
+notification.email.maplayer.deletefailed.subject={0}: Failed to delete WorldMap layer
notification.email.maplayer.deletefailed.text=We failed to delete the WorldMap layer associated with the restricted file {0}, and any related data that may still be publicly available on the WorldMap site. Please try again, or contact WorldMap and/or Dataverse support. (Dataset: {1})
-notification.email.submit.dataset.subject=Dataverse: Your dataset has been submitted for review
-notification.email.publish.dataset.subject=Dataverse: Your dataset has been published
-notification.email.returned.dataset.subject=Dataverse: Your dataset has been returned
-notification.email.create.account.subject=Dataverse: Your account has been created
-notification.email.assign.role.subject=Dataverse: You have been assigned a role
-notification.email.revoke.role.subject=Dataverse: Your role has been revoked
-notification.email.verifyEmail.subject=Dataverse: Verify your email address
+notification.email.submit.dataset.subject={0}: Your dataset has been submitted for review
+notification.email.publish.dataset.subject={0}: Your dataset has been published
+notification.email.returned.dataset.subject={0}: Your dataset has been returned
+notification.email.create.account.subject={0}: Your account has been created
+notification.email.assign.role.subject={0}: You have been assigned a role
+notification.email.revoke.role.subject={0}: Your role has been revoked
+notification.email.verifyEmail.subject={0}: Verify your email address
notification.email.greeting=Hello, \n
# Bundle file editors, please note that "notification.email.welcome" is used in a unit test
-notification.email.welcome=Welcome to Dataverse! Get started by adding or finding data. Have questions? Check out the User Guide at {0}/{1}/user/ or contact Dataverse Support for assistance. Want to test out Dataverse features? Use our Demo Site at https://demo.dataverse.org
+notification.email.welcome=Welcome to {0}! Get started by adding or finding data. Have questions? Check out the User Guide at {1}/{2}/user or contact {3} at {4} for assistance.
notification.email.welcomeConfirmEmailAddOn=\n\nPlease verify your email address at {0}. Note, the verify link will expire after {1}. Send another verification email by visiting your account page.
notification.email.requestFileAccess=File access requested for dataset: {0}. Manage permissions at {1}.
notification.email.grantFileAccess=Access granted for files in dataset: {0} (view at {1}).
notification.email.rejectFileAccess=Access rejected for requested files in dataset: {0} (view at {1}).
# Bundle file editors, please note that "notification.email.createDataverse" is used in a unit test
-notification.email.createDataverse=Your new dataverse named {0} (view at {1} ) was created in {2} (view at {3} ). To learn more about what you can do with your dataverse, check out the Dataverse Management - Dataverse User Guide at {4}/{5}/user/dataverse-management.html .
+notification.email.createDataverse=Your new dataverse named {0} (view at {1} ) was created in {2} (view at {3} ). To learn more about what you can do with your dataverse, check out the Dataverse Management - User Guide at {4}/{5}/user/dataverse-management.html .
# Bundle file editors, please note that "notification.email.createDataset" is used in a unit test
-notification.email.createDataset=Your new dataset named {0} (view at {1} ) was created in {2} (view at {3} ). To learn more about what you can do with a dataset, check out the Dataset Management - Dataset User Guide at {4}/{5}/user/dataset-management.html .
-notification.email.wasSubmittedForReview={0} (view at {1}) was submitted for review to be published in {2} (view at {3}). Don't forget to publish it or send it back to the contributor\!
+notification.email.createDataset=Your new dataset named {0} (view at {1} ) was created in {2} (view at {3} ). To learn more about what you can do with a dataset, check out the Dataset Management - User Guide at {4}/{5}/user/dataset-management.html .
+notification.email.wasSubmittedForReview={0} (view at {1}) was submitted for review to be published in {2} (view at {3}). Don't forget to publish it or send it back to the contributor\!
notification.email.wasReturnedByReviewer={0} (view at {1}) was returned by the curator of {2} (view at {3}).
notification.email.wasPublished={0} (view at {1}) was published in {2} (view at {3}).
notification.email.worldMap.added={0} (view at {1}) had WorldMap layer data added to it.
-notification.email.closing=\n\nThank you,\nThe Dataverse Project
+notification.email.closing=\n\nThank you,\n{0}
notification.email.assignRole=You are now {0} for the {1} "{2}" (view at {3}).
notification.email.revokeRole=One of your roles for the {0} "{1}" has been revoked (view at {2}).
notification.email.changeEmail=Hello, {0}.{1}\n\nPlease contact us if you did not intend this change or if you need assistance.
@@ -537,9 +532,9 @@ hours=hours
hour=hour
minutes=minutes
minute=minute
-notification.email.checksumfail.subject=Dataverse: Your upload failed checksum validation.
-notification.email.import.filesystem.subject=Dataverse: Your file import job has completed
-notification.email.import.checksum.subject=Dataverse: Your file checksum job has completed
+notification.email.checksumfail.subject={0}: Your upload failed checksum validation
+notification.email.import.filesystem.subject={0}: Your file import job has completed
+notification.email.import.checksum.subject={0}: Your file checksum job has completed
# passwordreset.xhtml
@@ -561,7 +556,7 @@ passwdReset.resetBtn=Reset Password
# dataverse.xhtml
-dataverse.title=The project, department, university, or professor this dataverse will contain data for.
+dataverse.title=The project, department, university, professor, or journal this dataverse will contain data for.
dataverse.enterName=Enter name...
dataverse.host.title=The dataverse which contains this data.
dataverse.identifier.title=Short name used for the URL of this dataverse.
@@ -666,7 +661,7 @@ dataverse.update.failure=This dataverse was not able to be updated.
# advanced.xhtml
advanced.search.header.dataverses=Dataverses
-advanced.search.dataverses.name.tip=The project, department, university, or professor this Dataverse will contain data for.
+advanced.search.dataverses.name.tip=The project, department, university, professor, or journal this Dataverse will contain data for.
advanced.search.dataverses.affiliation.tip=The organization with which this Dataverse is affiliated.
advanced.search.dataverses.description.tip=A summary describing the purpose, nature, or scope of this Dataverse.
advanced.search.dataverses.subject.tip=Domain-specific Subject Categories that are topically relevant to this Dataverse.
@@ -951,7 +946,7 @@ dataset.manageTemplates.tab.action.btn.delete.dialog.header=Delete Template
dataset.manageTemplates.tab.action.btn.view.dialog.header=Dataset Template Preview
dataset.manageTemplates.tab.action.btn.view.dialog.datasetTemplate=Dataset Template
dataset.manageTemplates.tab.action.btn.view.dialog.datasetTemplate.title=The dataset template which prepopulates info into the form automatically.
-dataset.manageTemplates.tab.action.noedit.createdin=Template created at {0} Dataverse
+dataset.manageTemplates.tab.action.noedit.createdin=Template created at {0}
dataset.manageTemplates.delete.usedAsDefault=This template is the default template for the following dataverse(s). It will be removed as default as well.
dataset.manageTemplates.info.message.notEmptyTable=Create, clone, edit, view, or delete dataset templates. Create a dataset template to prefill metadata fields with standard values, such as author affiliation, to help users create datasets in this dataverse. You can also add help text directly into the metadata fields to give users more information on what to add to these metadata fields.
@@ -1034,7 +1029,7 @@ dataset.manageGuestbooks.tab.action.btn.view.dialog.datasetGuestbook=Guestbook N
dataset.manageGuestbooks.tab.action.btn.viewCollectedData.dialog.header=Dataset Guestbook Collected Data
dataset.manageGuestbooks.tab.action.btn.view.dialog.userCollectedData.title=User data collected by the guestbook.
dataset.manageGuestbooks.tab.action.btn.view.dialog.userCollectedData=Collected Data
-dataset.manageGuestbooks.tab.action.noedit.createdin=Guestbook created at {0} Dataverse
+dataset.manageGuestbooks.tab.action.noedit.createdin=Guestbook created at {0}
dataset.manageGuestbooks.message.deleteSuccess=The guestbook has been deleted.
dataset.manageGuestbooks.message.deleteFailure=The guestbook cannot be deleted.
dataset.manageGuestbooks.message.editSuccess=The guestbook has been updated.
@@ -1383,11 +1378,11 @@ file.dataFilesTab.terms.list.termsOfAccess.addInfo.studyCompletion.title=Relatio
file.dataFilesTab.terms.list.guestbook=Guestbook
file.dataFilesTab.terms.list.guestbook.title=User information (i.e., name, email, institution, and position) will be collected when files are downloaded.
file.dataFilesTab.terms.list.guestbook.noSelected.tip=No guestbook is assigned to this dataset, you will not be prompted to provide any information on file download.
-file.dataFilesTab.terms.list.guestbook.noSelected.admin.tip=There are no guestbooks available in {0} Dataverse to assign to this dataset.
+file.dataFilesTab.terms.list.guestbook.noSelected.admin.tip=There are no guestbooks available in {0} to assign to this dataset.
file.dataFilesTab.terms.list.guestbook.inUse.tip=The following guestbook will prompt a user to provide additional information when downloading a file.
file.dataFilesTab.terms.list.guestbook.viewBtn=Preview Guestbook
file.dataFilesTab.terms.list.guestbook.select.tip=Select a guestbook to have a user provide additional information when downloading a file.
-file.dataFilesTab.terms.list.guestbook.noAvailable.tip=There are no guestbooks enabled in {0} Dataverse. To create a guestbook, return to {0} Dataverse, click the "Edit" button and select the "Dataset Guestbooks" option.
+file.dataFilesTab.terms.list.guestbook.noAvailable.tip=There are no guestbooks enabled in {0}. To create a guestbook, return to {0}, click the "Edit" button and select the "Dataset Guestbooks" option.
file.dataFilesTab.terms.list.guestbook.clearBtn=Clear Selection
file.dataFilesTab.versions=Versions
@@ -1460,6 +1455,10 @@ file.viewDiffDialog.description=Description
file.viewDiffDialog.fileReplaced=File Replaced
file.viewDiffDialog.filesReplaced=File(s) Replaced
file.viewDiffDialog.files.header=Files
+file.viewDiffDialog.msg.draftFound= This is the "DRAFT" version.
+file.viewDiffDialog.msg.draftNotFound=The "DRAFT" version was not found.
+file.viewDiffDialog.msg.versionFound= This is version "{0}".
+file.viewDiffDialog.msg.versionNotFound=Version "{0}" was not found.
file.metadataTip=Metadata Tip: After adding the dataset, click the Edit Dataset button to add more metadata.
file.addBtn=Save Dataset
file.dataset.allFiles=All Files from this Dataset
diff --git a/src/main/java/edu/harvard/iq/dataverse/AbstractIdServiceBean.java b/src/main/java/edu/harvard/iq/dataverse/AbstractIdServiceBean.java
index 9142893f7cb..1ee5fabbbcc 100644
--- a/src/main/java/edu/harvard/iq/dataverse/AbstractIdServiceBean.java
+++ b/src/main/java/edu/harvard/iq/dataverse/AbstractIdServiceBean.java
@@ -53,7 +53,7 @@ protected HashMap addBasicMetadata(Dataset datasetIn, HashMapGET
+ SAMPLE HEADER LINK
+ ![#{bundle['footer.dataverseProject']}](/resources/images/dataverseproject_logo.jpg){kind=logo}
![#{bundle['footer.dataverseProject']}](/resources/images/dataverseproject_logo.png){kind=logo}