Skip to main content
Skip table of contents

R28 Impact and Requirements

19 June 2018

ANDS Online Services Release 28 is due for implementation on Wednesday, 4 July 2018.  Please find below the summary of all Release 28 changes with an overview of who, what and how the changes will impact our users.

Research Data Australia (RDA)

Change: Integrate Relationship Graph to RDA view pages

  • Details: Integrate relationship graph to RDA view pages
  • Impact: (low) Within the record view page, RDA users will start to see a visual presentation of a record's relationships through the new relationship graph. Each node on the graph will provide users with some basic information about the related entity and will allow them to easily navigate to a linked page (e.g ORCID page, RDA page, etc.), as applicable. If no related object exists for that record, the graph will be hidden from view.
  • Action required:
    • No action required from RDA users.
    • No immediate action required from RDA contributors however, in order to take advantage of this new functionality, ANDS highly recommend that linkages and relationships are properly encoded or defined in RDA records. Refer to the Content Providers Guide's Related Object and Related Information pages for more information.
  • Communications and Support:
    • Release announcements will be sent to ANDS staff, Data Source Administrators, ANDS partners, and general users.
    • Documentation will be published with updated procedures and release notes: Online Services Technical Updates.

Change: Update the RDA party view page to ensure that the electronic address is displayed when provided in RIF-CS

  • Details: RDA party records (researchers, groups, organisations) will be enhanced to display a navigable link to the record's electronic address (i.e a URL) when provided in RIF-CS.
  • Impact: (low) RDA users will now be allowed to navigate to a researcher's or organisations web page from within the record view page in RDA.
  • Action required: No action required from all users.
  • Communications and Support:
    • Release announcements will be sent to ANDS staff, Data Source Administrators, ANDS partners, and general users.
    • Documentation will be published with updated procedures and release notes: Online Services Technical Updates.

Change: Change the label 'Go To Data Provider' to 'Access Data' in RDA view page and update the display to emphasise a clickable button

  • Details: The button to get to the collection record's data (via a landing page or direct download) labeled 'Go To Data Provider' will be changed to 'Access Data' and the look and feel of the button will be changed for improved visibility.
  • Impact: (low)
    • RDA users will now be able to easily identify the link to access the data described in the record view page.
    • Service desk issues coming from users who were asking for instructions on how the data in RDA is accessed are expected to drop over time.
  • Action required: No action required from all users.
  • Communications and Support:
    • Release announcements will be sent to ANDS staff, Data Source Administrators, ANDS partners, and general users.
    • Documentation will be published with updated procedures and release notes: Online Services Technical Updates.

Change: Properly index collections without licence type under 'Other' rather than 'Unknown'

  • Details: Simplify RDA search filters for licence type by ensuring that all records without licence type are indexed under 'Other'. These records are currently being indexed under 'Unknown'.
  • Impact: (low) Filtering of records by licence type will be made easier and less confusing. All records without a licence type and those that are outside the controlled list will now be consolidated under 'Other' type.
  • Action required: No action required from all users.
  • Communications and Support:

Change: Enhancements to the Broken Link tool

  • Details: 
    • Enhancements to the link extraction process to identify and strip characters unintentionally included in description URLs
    • Prevent draft records from being included in the Broken Links report
  • Impact: (low) The next broken link report will have less false-positives making it easier for Data Source Administrators and DOI contacts to read the report and identify true unresolvable links.
  • Action required:
    • No action required from RDA users.
    • The next broken link tool for RVA and RDA will be run after the release. RDA contributors and DOI clients are expected to resolve broken links reported by the tool.
  • Communications and Support:
    • Release announcements will be sent to ANDS staff, Data Source Administrators, ANDS partners, and general users.
    • Documentation will be published with updated procedures and release notes: Online Services Technical Updates.

Change: Fix bug in query for 'Last 5 Datasets' section on Contributor pages

  • Details: The Solr query that generates the list of collections for the 'Last 5 Datasets' section is being sorted on an old time stamp field. The query will be updated to sort using the correct field.
  • Impact: (low)  he 'Last 5 Datasets' section will correctly display the latest 5 collection records
  • Action required: No action required from RDA users.
  • Communications and Support:
    • Release announcements will be sent to ANDS staff, Data Source Administrators, ANDS partners, and general users.
    • Documentation will be published with updated procedures and release notes: Online Services Technical Updates.

DOI Service

Change: New Functionality: Transfer of DOI ownership

  • Details: 
    • New functionality that will allow users to transfer ownership (hosting and management) of DOIs will be made available to all clients.
    • The transfer of ownership will be done through ANDS Services. Authority to transfer (the agreement between the transferor and the transferee) shall be provided to ANDS before a transfer can be initiated.
  • Impact: (low) Transferred DOIs will stop appearing in the transferor’s My DOIs as they will now appear under the transferee’s My DOIs.
  • Action required: There is no immediate action required from any client unless there is a need to transfer the  ownership of a DOI to another client. If you need to transfer a DOI, simply send an email to services@ardc.edu.au to initiate the transfer.
  • Communications and Support:

Change: Assignment of individual DOI prefix per client

  • Details: 
    • Current setup: There are currently 3 ANDS production DOI prefixes (10.4225, 10.4226 and 10.4227) shared among all clients.
    • Proposed setup: The list of prefixes will be expanded so that each client is allocated with a separate DOI prefix.
  • Impact: (low)
    • Each client will mint DOIs under a different prefix reducing the possibility of identifier clashes between clients.
    • While each client will mint under separate prefixes these will not be used to represent an organisation/institution (see Transfer of DOI Ownership details above).
    • Clients who are using the DOI prefix in their system for things like reporting, searching, etc. should start planning for any possible system update.
  • Action required: 
    • There is no action required from clients. New DOIs will automatically be minted with the allocated prefix. DOIs minted with previously allocated prefixes can still be updated.
    • Clients using the ANDS DataCite Client API and generating their own DOI strings should plan for the update of the DOI Prefix. Minting of DOIs with the existing prefix will continue to work until the new prefix can be implemented by the client. ANDS services will contact the clients using this API to assist with the transition.
  • Communications and Support:
    • Release announcements will be sent to ANDS staff, Data Source Administrators, ANDS partners, and general users.
    • All DOI service users will be contacted prior to implementation for feedback.
    • ANDS Services will ensure that existing client registrations are updated with the new prefixes.
    • Documentation will be published with updated procedures and release notes: Online Services Technical Updates, DOI Service Technical Documentation.

Change: Implementation of a single Test account for all clients

  • Important: This change has been postponed until a later release. More details will be sent in a separate email to DOI users.

Change: Removal of the client ID from DOIs

  • Details: 
    • Current setup:  At the time of registration for an ANDS DOI account each client is allocated a specific Client ID (a 2-digit code representing an organisation) in the ANDS DOI system. This ID is then used as part of each DOI string (eg, 10.5072/01/05E7F1ED6B).
    • Proposed setup: As a result of the introduction of the DOI ownership transfer functionality, inserting the Client ID in the DOI string will no longer be useful.  A particular client ID may now appear in more than one organisation’s DOI list after an ownership transfer. Therefore the ANDS DOI service will no longer include the Client ID in DOI strings.
  • Impact: (low)  New DOIs minted via the My DOIs interface or the ANDS DOI M2M service will not have the client ID as part of the identifier. The DOI structure will simply be the prefix + suffix e.g. 10.5072/4DD05E7F1ED6B (previously, 10.5072/01/05E7F1ED6B).
  • Action required: 
    • Clients who are using the 2-digit client ID in their system other than it being part of the DOI unique string (e.g. for reporting, searching, etc.) should start planning for the removal of the client ID as a reference.
    • Clients using the ANDS DataCite Client API and generating their own DOI strings should plan for the removal of the Client ID as part of the DOI Prefix. Minting of DOIs with the Client ID as part of the prefix will continue to work but should be phased out as soon as it is feasible.
  • Communications and Support:

Change: Implementation of an API endpoint that returns the status of the DOI

  • Details: A new endpoint will be added to the ANDS DOI API which allows users to retrieve the status of their DOIs.
  • Impact: (low) Use of the end point to retrieve the status of a DOI is optional and can be used if and as needed.
  • Action required: No action required from all users.
  • Communications and Support:

Change: Validation of the response code/message received from DataCite after client creation or update

  • Details: DOI Administration: Validation of the response code/message received from DataCite after creation or update of a DOI client
  • Impact: (low) DOI users will no longer receive DOI minting or update errors resulting from failed client registration creation/update. The ANDS DOI Administrator will now be notified if such an error occur during the client registration or update process.
  • Action required: No action required from all users.
  • Communications and Support:

Research Vocabularies Australia


Change: Implement a functionality that will allow RVA portal registered users to receive notifications for RVA updates

  • Details: Implement a functionality that will allow RVA portal registered users to receive notifications for RVA updates such as an addition of new vocabulary, an addition of a new version of a vocabulary, etc.
  • Impact: (low) Subscription to RVA notification is optional.
  • Action required: No immediate action is required.
  • Communications and Support:
    • Release announcements will be sent to ANDS staff, Data Source Administrators, ANDS partners, and general users.
    • Documentation will be published with updated procedures and release notes: Online Services Technical Updates.

Change: Fix bug where import from PoolParty fails if metadata contains new related entities

  • Details: When creating a new vocabulary in RVA that is linked to a PoolParty project that contains related entities that do not exist in RVA, the system request to create the related entities is sent before the user has selected a vocabulary owner, resulting in an error. This change will ensure the request to create related entities is sent after the owner has been confirmed.
  • Impact: (low) Users will no longer receive errors when linking to a PoolParty project.
  • Action required: No action is required.
  • Communications and Support:
    •  
    • Release announcements will be sent to ANDS staff, Data Source Administrators, ANDS partners, and general users.
    • Documentation will be published with updated procedures and release notes: Online Services Technical Updates.

New IGSN Service

Change: Implement an International GeoSample Number (IGSN) service

  • Details: 
    • The purpose of this change is to implement an IGSN service to support the requirements of the Geoscience Research Data Clouds (RDC) and Data enhanced Virtual Laboratories (DeVL) project.
    • The Australian earth science academic community will be able to assign IGSN identifiers to geophysical samples associated with an Australian research activity such as rock, soil and sediment.
  • Communications and Support:

IMPORTANT:

The following changes are not included in Release 28. These changes will be implemented at a later date.

  • Support multilingual vocabularies in vocabulary widget
  • SISSVoc definitions: Change dcterms:created/modified to have range xsd:dateTime


If you have any questions or comments, please email services@ardc.edu.au.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close