2.1.1

Bug fixes:

• Each member node in the member node list on the data search page was repeated multiple times
• There were still some references in the code to window.location.hash which are no longer used
• Queries sent via the URL query parameter were not working
• Clicking the Download All button caused a redirect page to the default route (usually /data)

See the full list of issues in the 2.1.1 milestone.

2.1.0

Important: MetacatUI installation and upgrade steps have changed with this release. Please read the updated installation instructions before use.

MetacatUI 2.1.0 includes three new exciting features

1. MetacatUI now speaks Highwire Press! From dataset landing pages, you should be able to use some web-based reference importers, notably Mendeley's extensions and Zotero's importer bookmarklet, to automatically import relevant dataset citations details into those reference managers. This also paves the way for Google Scholar, if Google ever decides to start indexing datasets.

2. Dataset landing pages now show the number of downloads, views, and citations for datasets in participating DataONE member repositories.

3. Navigation by real pathnames rather than hash string (e.g. /data/page/2 rather than #data/page/2) which also allows all MetacatUI views to be indexed by Google as webpages. This change depends on an Apache configuration change.

For a full list of changes, see the 2.1.0 milestone.

New installation instructions

1. New Apache configuration required

The new routing changes work because when a client navigates to a MetacatUI view via a full pathname (/data) rather than a hash (/#data), Apache will serve the MetacatUI index.html page as a fallback resource instead of returning a 404 error. The fallback resource is specified via this Apache setting:

FallbackResource /index.html

Example Apache config:

<VirtualHost  *:443>
   
    DocumentRoot /var/www/my-site.com/
    ...
   <Directory "/var/www/my-site.com/metacatui">
         FallbackResource /metacatui/index.html
  </Directory>

</VirtualHost>

The FallbackResource directive requires your Apache version to be 2.2.16 and above. If you're using the earlier versions of Apache, you'll require mod_rewrite in your configuration. Example:

  <Directory "/var/www/my-site.com/metacatui">
  ...
  ...

  <IfModule mod_rewrite.c>
      RewriteEngine On
      RewriteBase /
      RewriteRule ^index\.html$ - [L]
      RewriteCond %{REQUEST_FILENAME} !-f
      RewriteCond %{REQUEST_FILENAME} !-d
      RewriteRule . /index.html [L]
  </IfModule>
  </Directory>

2. The MetacatUI root URL needs to be specified

A MetacatUI.root variable also needs to be set in MetacatUI, now. The default MetacatUI.root is /metacatui, which is the default installation location for MetacatUI when installed with Metacat.

If your MetacatUI is located at a different URL than /metacatui (e.g. https://my-site.com or https://my-site.com/catalog), then two things needs to be changed:

1. In index.html, set the URL for the loader.js script to the absolute URL of your MetacatUI loader.js file. (e.g. /loader.js or /catalog/loader.js or https://my-site.com/loader.js).

2. Set the MetacatUI.root variable in loader.js to the MetacatUI root location. e.g. / or /catalog or /loader.js)

2.0.0

Major new features

Metadata Editor

The new metadata editor replaces the Perl editor bundled with Metacat and MetacatUI 1.X. Because it is entirely client-based, it works independently of the Metacat software.

The new metadata editor contains fields for entity and attribute-level metadata, as well as other improvements over the old Perl editor.

Provenance Editor

The provenance editor is a visual editor for adding provenance relationships between objects in a data package.

Default theme cleanup

The default theme styling was cleaned up and simplified to make it easier to read and use.

1.14.17

Fixes a bug where equivalent identities were not being queried correctly in the user profiles because the DataONE accounts service sometimes uses uppercase letters in DN's in the <equivalentIdentity> node and lowercase in the person's <subject> node. Example: https://cn.dataone.org/cn/v2/accounts/http%3A%2F%2Forcid.org%2F0000-0002-5944-906X

2.0.0 Release Candidate 15

Bug fixes:

• Fixed Editor save error: Invalid content was found starting with element 'sampling'. One of '{methodStep}' is expected.
• Switching units only didn't cause the Submit button to display and didn't get serialized in the EML
• Switching an attribute from code list to particular text didn't serialize correctly
• Fixed Editor save error: EMLSAXHandler.writeOnlineDataFileIdIntoRelationTable(): ERROR: duplicate key value violates unique constraint "xml_relation_uk"
• When the entity name was missing, there was no error message displayed
• EML packageId was not being updated when the EML id was updated in the editor
• When adding a new person type, the person was serialized twice in the EML.
• Attribute error message didn't go away in Safari until starting on the next attribute
• Submit button was displaying immediately after submitting the package, even though no changes have been made yet
• EMLDataTable models were not validating their attributes during validate(), causing EML save errors

Enhancements:

• The EML file name is now set to the EML title each time it is saved

For the full list of changes, see the 2.0.0 RC 15 milestone: https://github.com/NCEAS/metacatui/milestone/34

2.0.0 Release Candidate 14

Bug fixes:

• Fixed Editor bug when serializing reserved XML characters.
• Fixed bug where removing data files caused save errors and did not remove the corresponding entity.

For the full list of change, see the 2.0.0 RC 14 milestone

2.0.0 Release Candidate 13

Save a copy of the EML as a plain text data object when it fails to save, so that users don't loose all their work.

1.14.16

Fixed bugs related to sending and accepting identity map requests.

For a full list of changes, see the 1.14.16 milestone.

2.0.0 Release Candidate 12

Bug fixes:

• Added stability to the EML serialization to prevent duplicate ids.
• Search result rows will use the singular term "region" when there is only one geographic region on the map.

This pre-release is safe to use with production data in a Beta environment.

See the full list of changes in the 2.0.0 RC 12 milestone.

2.0.0 Release Candidate 11

• Fixed bugs where certain metadata fields were not removed when the text content of the input field was removed. (Only the remove buttons were working).
• Fixed the EMLText model so that special formatting is not removed unless the text content has changed.

This pre-release is safe to use with production data in a Beta environment.

For a full list of changes, see the 2.0.0 RC 11 milestone.