The Manage Records page is an interactive dashboard that allows you to manage all of the records in your data sources in one place. The following sections in this help guide explain how each of the main features function.
The ORCA Registry Publishing Workflow is used to manage the lifecycle of records within the registry. The workflow can be configured to be either very basic, where the user manages their records in only two statuses 'Draft' and 'Published, or more involved where the user is required to manage their records through an assessment workflow with a handful of statuses and a review process. The Manage Records page is the main interface to the publishing workflow, allowing users to manoeuvre their records through the valid record statuses.
The Basic workflow is extremely simple, only requiring that records contain no errors before being published. Users manage their records using two statuses 'Draft' and 'Published'. Having the 'Draft' status allows users to save records while working on them across sessions.
The diagram below illustrates the publishing process for data providers who are not required to have their records assessed by ANDS prior to publishing.
Note: Harvested records are automatically approved by the system.
Records are either auto published by the system or manually by the user. See 'Manually Publish Records' section below.
The Quality Assessment workflow allows ANDS to incorporate a level of quality assessment and approval within the record publishing process (both manual and harvest). The assessment workflow is only intended for new data providers who are gathering an understanding of the RIF-CS schema and ANDS metadata best practices.
In order to prevent records from being automatically published a 'Quality Assessment Required' flag has been set up in all data source accounts within ORCA. Setting the flag for a data source will force all manually created/edited and harvested records through the quality assessment workflow before they can be published. The flag is set by default for all newly created data source accounts and can only be changed by ANDS staff with the appropriate ORCA roles.
Once ANDS believes that a data provider has a good understanding of RIF-CS and best practices, the flag can be cleared allowing any future records to be managed through the Basic workflow.
The diagram below illustrates the publishing process for data providers who are required to have their records assessed by ANDS prior to publishing. Each stage of the workflow is either managed through the Manage My Records or Add Record (manual entry) screens.
Note: Harvested records are automatically submitted for assessment upon ingest.
To control which data sources are required to publish their records through the Quality Assessment workflow a 'Quality Assessment Required' flag has been set up in all Data Source Accounts. The flag is set by default for new accounts and can only be managed by ANDS staff with the appropriate ORCA roles. Having the flag checked (On) for a data source will force all manually created, edited and harvested records through the Quality Assessment workflow. Once ANDS believes that a data provider has a good understanding of RIF-CS and best practices, the flag can be cleared allowing any future records to be automatically approved.
Having the quality assessment flag at the data source account level may affect aggregators who provide ANDS with data through a single data source. The situation may arise where an aggregator has had part of its data source approved for direct publish access to Research Data Australia while another part is still in the assessment period. As the flag is set at the data source record level all records from the aggregator will be sent through the quality assessment process, possibly holding up previously approved records. Aggregators should discuss how to manage these issues with their ANDS contact.
The Assessment Notification Email field is used to enter the email addresses of ANDS Quality Assessors for a data source. The field is only available when the 'Quality Assessment Required' flag has been checked (On) and can only be managed by ANDS staff with the appropriate ORCA roles. Multiple email addresses can be entered by separating them with a comma. The address will be used in notifying the assessor(s) when a data source's records are submitted for assessment.
Note: If records from a data source are already in a status of 'Submitted for Assessment' (email has been sent) and the data source administrator submits further records for assessment, an additional email will not be sent. This is to prevent numerous emails being sent when a data source administrator is submitting records on a record by record basis.
return to menuIn some situations data providers may be required to have their records assessed and approved by ANDS but do not want to have them published immediately to Research Data Australia. For these users a 'Manually Publish Records' flag has been set up in all data source records within ORCA. Having the flag checked (On) will prevent records automatically moving from 'Approved' to 'Published' after being approved by a Quality Assessor. Users will need to use the Manage My Records screen to move these records to 'Published'. The flag will not be set by default.
The 'Manually Publish Records' flag will also be useful for approved providers (not required to have their records assessed by ANDS) who wish to test their harvest and view the records in ORCA. By checking the flag (On) the providers harvested records will be held at a status of 'Approved' and will not be visible in Research Data Australia. The provider then has the option to either, delete the records, remove the flag and re-harvest, or publish the records manually via the Manage My Records screen.
return to menuThe following table lists the record statuses used in the ORCA Publishing Workflow.
| Status | Definition |
|---|---|
| Draft | The record is still being worked on by the user. |
| Submitted for Assessment | The record has been submitted for assessment. |
| Assessment in Progress | The record is currently being assessed by an ANDS Quality Assessor. |
| More Work Required | The record has been assessed by an ANDS Quality Assessor who has determined that further work is required on the record. |
| Approved | The record has been approved by ANDS. These records are not visible in Research Data Australia. |
| Published | The record has been published. These records are visible in Research Data Australia. |
| Deleted | The previously 'Approved' or 'Published' record has been deleted. These records can be restored via the history tool. |
| Record Behaviour | Draft | Submitted for Assessment | Assessment in Progress | More Work Required | Approved | Published | Deleted |
|---|---|---|---|---|---|---|---|
| Changes status to 'Draft' upon edit | NA | ✔ | ✔ | ✔ | ✔ | X | X |
| Creates duplicate 'Draft' record upon edit | NA | X | X | X | X | ✔ | X |
| Can be restored via Deleted Records page | X | X | X | X | X | ✔ | NA |
| Discoverable in Research Data Australia | X | X | X | X | X | ✔ | X |
| Visible on Manage My Records screen if data source is not flagged as requiring Quality Assessment | ✔ | X | X | X | ✔ | ✔ | X |
| Visible on Manage My Records screen if data source is flagged as requiring Quality Assessment | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
The Metadata Content Report is a set of recommended RIF-CS elements for each of the record class types (collection, party, activity & service). The report has been implemented to assist users in creating rich metadata records that align with best practices.
To assist ANDS staff and data providers in validating that records being published to Research Data Australia meet the minimum set of requirements, the Metadata Content Report has been integrated into the ORCA Registry as a series of automated tests. The tests are conducted on records upon ingest to the registry (harvest or manual entry), and the resulting information stored with each record for reporting purposes on the Manage Records page.
On ingest to the ORCA registry, each record is validated against the Metadata Content Report business rules.
Each record's metadata report information is then made available via a report icon
on the Manage Records page.
To quickly assess a record's Metadata Content Report without viewing the complete record:

The following section outlines the available record selection methods which can be used on the Manage Records page.



Note: You can also use this method combined with the ungrouped method outlined below to select multiple records.

Note: You can also use this method combined with the grouped method outlined above to select multiple records.


In order to view a record listed on the Manage Records page, use either of the following methods.

OR

In order to edit a record listed on the Manage Records page, use either of the following methods.
Note: Not all registry users will be able to edit all of the statuses shown on the Manage Records page. The option to edit will only be shown where the logged user has the appropriate privileges.

OR

The following section outlines the available methods which can be used to move records through the publishing workflow
Note: Not all registry users will be able to carry out all of the status moves on the Manage Records page. The option to change a records status will only be shown where the logged user has the appropriate privileges.

OR
Drag & Drop

Note: Not all registry users will be able to carry out all of the status moves on the Manage Records page. The table will highlight blue where the move is permitted. Some registry users will be able to drag and drop records backwards in the workflow (e.g. From 'Assessment in Progress' to 'More Work Required').
OR


OR
Drag & Drop

Note: Not all registry users will be able to carry out all of the status moves on the Manage Records page. The table will highlight blue where the move is permitted. Some registry users will be able to drag and drop records backwards in the workflow (e.g. From 'Assessment in Progress' to 'More Work Required').
return to menuThe following section outlines the available methods which can be used to delete records from the Manage Records page.
Note:

shown with each selected record.
The Flag feature on the Manage Records page gives you the ability to mark records with an icon which represents a level of importance or grouping (similar to flags used in email applications). The flag is stored with the record and is therefore remembered over your separate logins. Filtering and selection options then allow you to quickly action all of the records you have flagged.

shown with each selected record.
Note: If one or more of the records in your selection have already been flagged you will need to remove the flag(s) before the 'Flag' option will be displayed in the contextual menu.
shown with each selected record.

By default the record tables display a maximum of 20 records. Where more than 20 records exist in a table a 'Show More' tab will be displayed below the last record. Simply click the tab and the next 20 records will be appended to the table.

Tip: When trying to locate a record in a table with a large number of records, it is often much quicker to use the filter options outlined below.
return to menuTo assist you in locating records in record tables with large numbers, a search filter has been incorporated into page.
To conduct a search:

A number of predefined record attribute filters are available on the Manage Records page to assist you in locating records.
To filter the tables by a specific attribute:

Two predefined sorting options are included with the Mange Records page 'Date Modified' and 'Quality Level'. By default the tables will be sorted by 'Date Modified' descending.
To sort the records tables by a predefined sort option:

If you are experiencing any issues with the page or have questions/comments, please email services@ands.org.au. A JIRA ticket will automatically be raised for your request and you will receive an email from the JIRA system with a link to the ticket. Opening the link to the ticket allows you to track and update the issue. You will also receive emails from the system whenever the ticket is updated.