Page Comparison

Overview

The version 5.2 release includes upgrades to service layer components, new (to version 5) profiles, enhancements to reporting and batch processing, and many bug fixes.

...

• Enhancements to reporting and batch processing
  • A new top-level tab, "Tools", has been added to the UI. The "Term Lists" tab, previously under the top-level Adminstration screen, has been moved to Tools. The Tools screen also contains two new tabs, "Reports" and "Data Updates", which list the reports and batch jobs that are installed in the system. On these tabs, users can view and edit report/batch job metadata, and invoke the reports and batch jobs. 

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-616

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-650

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-652

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-722

  • Reports and batch jobs can now be run in "no context" mode through the UI. Previously, "no context" invocation was only possible using the REST API. A "no context" invocation causes the report/batch job to run on all records, or on a subset of records that is not selected by the end user. To invoke a report or batch job in "no context" mode, select the report/batch job on the Tools screen, click the Run button, and select "Run on all records". For this to work, the report/batch job must be authored to support no-context mode invocation. 

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-616

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-650

  • Reports and batch jobs can now be run in "record list" mode through the UI. Previously, "record list" invocation was only possible using the REST API. To invoke a report or batch job in "record list" mode, perform a search, and select (check) one or more of the results. The right sidebar on the search result page is populated with lists of reports and batch jobs that are registered for the record type displayed in the search results, and that support the "record list" invocation mode. Clicking on one of the items in the list will invoke the report/batch job in "record list" mode, on the selected (checked) records. 

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-653

  • Reports and batch jobs can now be run in "group" mode through the UI. Previously, "group" invocation was only possible using the REST API. A "group" invocation causes the report/batch job to run on records related to the group. To invoke a report or batch job in "group" mode, open a Group record. The right sidebar is populated with lists of reports and batch jobs that are registered for Group records, and that support either the "single record" or "group" invocation mode. Click on one of the items. If "group" mode is supported, the "Run on group" option will be available. Select that option to run the report/batch job in "group" mode. 
  • When running a report or batch job from the Tools screen in the UI, the user can select any invocation mode supported by the report/batch job. If the selected mode is "record list", "group", or "single record", the user will be prompted to search for and select records on which to run the report/batch job. 

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-651

  • When running a report or batch job, the UI can now display a form for the user to enter parameters to pass to the invocation. The report/batch job must be authored to accept parameters, and the UI must be configured with a form template to use to display the inputs for that particular report/batch job.

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-558

  • It is now possible to specify the desired output format for a report invocation.
    • The invocation context payload sent to the REST API may now contain an outputMIME element. If specified, the outputMIME of the invocation context is used as the output format of the report invocation. Otherwise, the outputMIME of the report is used as the default output format.
    • When running a report, the UI now displays a dropdown to allow the user to select the desired output format. 

      Jira Legacy
      showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-675

• Roles can now be searched by display name. 
  • In the REST API, the roles endpoint now accepts the dn parameter, for example: /cspace-services/authorization/roles?dn=admin. Previously, the roles endpoint only supported the r parameter for searching by the internal role name, which is different than the display name. The r parameter and the dn parameter are mutually exclusive; supplying both will result in an error. 

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-497

  • In the UI, the list of roles in the Roles and Permissions tab of the Administration screen now allows filtering by display name (labeled as just "name", because the internal role name is never displayed to the end user). 

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-676

• A REST API call has been added to rebuild the Elasticsearch index (if Elasticsearch indexing is enabled). A POST request to /cspace-services/index/elasticsearch will cause the index to be deleted, the mappings to be resent, and all records to be reindexed. Currently, only the built-in admin user is permitted to execute this request. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-656

• An error message is now displayed in the footer of the UI when server status information can not be retrieved. Instead of showing the version of the CollectionSpace server (e.g. "Release 5.2"), the message "Not connected to <url>" is shown, where <url> is the URL that the UI is attempting to use to connect to the REST API. This message often indicates that the CollectionSpace server is not running. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-661

• The spinner icon is now displayed next to the "Signing in" message while a login is in progress. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-662

...

• On the Object record, a new field has been added to the Object Collection Information section: Field Collection Schema. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-620

• Anthropology profile: 
  • A new procedure has been added: Osteology. 

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-617

  • On the Person record, a new field has been added: Person Type. 

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-400

  • On the Object record, a new field group has been added to the Object Description Information section: Commingled Remains. 

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-618

  • On the Object record, a new field group has been added to the Repatriation and NAGPRA Compliance Information section: Reported to National NAGPRA. 

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-621

  • On the Object record, a new field group has been added to a new section: Locality Information. 

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-400

...

• The presence of deprecated ("inactive") terms on a shared authority server no longer causes synchronization to fail. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-437

• The number of narrower records displayed in the Hierarchy section is no longer limited to 40. This change can cause records with many child records to take a long time to load; this will be addressed in a future release. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-660

• Authority terms deleted on a shared authority server no longer appear in term completion results. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-428

• When a Location/Movement/Inventory record is selected from search results and related to other records, the message that is displayed when the relation completes now contains the correct title of the L/M/I record. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-495

• Chrome's autofill menu no longer appears on certain fields that appear inside tables. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-624

• Today's date is now highlighted in the calendar date picker. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-625

• In the Term Lists tab of the Administration screen, terms lists are now sorted by name. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-682

• In the Term Lists tab of the Administration screen, terms in a term list are now sorted case-insensitively when the Name header is clicked. Previously, they were sorted case-sensitively. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-642

• The Reports and Data Updates listings in the sidebar of a record now show only reports/batch jobs that are registered to run in "single record" mode – except on Group records, where reports/batch jobs that support "group" mode are shown as well. Previously, reports/batch jobs were shown regardless of the supported invocation mode, even though the mode used to run a report/batch job from the record sidebar was always "single record". 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-654

• Advanced search with multiple "and" fields ("All of the following conditions must be satisfied" is selected), where one of the fields has multiple "or" values, now produces correct results. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-671

• Cloned person and organization records can now be successfully updated without error. 

  Jira Legacy
  showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-721

• Public art profile:
  • Terms entered into the Commissioning Body field now appear in the Terms Used sidebar. 

    Jira Legacy
    showSummary false server System JIRA serverId 4f23a7bf-fe0d-390f-9b92-bdff15338913 key DRYD-713

...