What’s new in ECS Cataloging and Search

Contacts: Christine Schultz-Richert

Inventory Search & Browse

Search and browse through local and shared instances and local holdings/items (UXPROD-4138 & UXPROD-4241)

Held by & Shared facet

Description: Added two new facets to allow users to filter shared vs local records as well as filter records by which member libraries have holdings on shared records. An icon was also added to the search results pane to indicate if a record is shared.

Important considerations:

• The “Shared” facet is only available on member tenants, as only shared records will be discoverable in the central tenant

• The “Held by” facet is not available for Contributors and Subject browse

Changes/additions: In order to view shared records from a member tenant, users must have the appropriate permissions in the central tenant.

Known limitations:

• Note that in the production environment, the central tenant (“Consortium” in screenshot) will NOT show in the Held by facet as the central tenant can't currently have any holdings or items

• In the find instance plugin, the Held by facet does NOT currently filter to the corresponding locations in the effective location facet. This will require additional work on the plugin.

Actions required: None.

Effective location (item) facet

Description: Like single-tenant environments, this facet will display the effective locations for items on Shared or Local Instances (depending on selection in Shared facet).

Important considerations:

Changes/additions: In order to view effective locations from other tenants in this facet, the user needs to have view permissions in the corresponding tenant.

Known limitations:

• The ability to view all effective locations regardless of permissions is currently not supported. This is being considered for future releases

Actions required: None.

MARC authority

Search and browse shared and local MARC authority records (UXPROD-4139)

Description: Like the Inventory app, a “Shared” facet has been added to the MARC authority app to allow users to filter shared vs local MARC authority records. The same icon was also added to search results to indicate that a record is shared.

Important considerations:

• The “Shared” facet is only available on member tenants, as only shared records will be discoverable in the central tenant

Changes/additions: In order to view shared records from a member tenant, users must have the appropriate permissions in the central tenant.

Known limitations: None.

Actions required: None.

Sharing MARC authority records (UXPROD-4278)

Description: MARC authority records can be shared to the rest of the consortium members by importing the records via Data import in the central tenant. If an authority record is imported via Data import in a member tenant, the record will be local only.

Changes/additions: None.

Known limitations: In this release -

• Shared MARC authority records cannot be updated via Data import in a member tenant

• There is no action to share a local MARC authority record

Actions required: None.

Identifying a MARC authority record as shared or local (UXPROD-4265)

Description: When viewing a MARC authority record in the MARC authority app, the user will be able to identify the shared status of the record with new “Shared” or “Local” text on the record and in the paneheader.

Changes/additions: None.

Known limitations: None.

Actions required: None.

quickMARC

Create new shared or local MARC bibliographic record (UXPROD-4316)

Description: Utilizing the functionality to create a new MARC bibliographic record in the quickMARC UI, this same functionality can be used in an ECS-enabled environment to create a new shared or local MARC bib record. If the user creates a new MARC bib record in the central tenant, this record will be shared. Conversely, if the user creates a new MARC bib record in a member tenant, the record will be local. Note that once a new local MARC bib and the corresponding instance are created, this record is eligible to be promoted to shared.

Changes/additions: Must have the new permission “quickMARC: Create a new MARC bibliographic record” in the applicable tenant(s)

Known limitations: None.

Actions required: None.

Derive a shared or local MARC bib record from a shared instance record (UXPROD-4212)

Description: The ability to derive a new record from a shared instance record is supported. If the user is deriving from a shared record in the central tenant, a new shared record will be created. Conversely, if the user is deriving from a shared record in a member tenant, a new local record will be created.

Changes/additions: None.

Known limitations: None.

Actions required: None.

Editing a shared MARC bib record in quickMARC (UXPROD-4213)

Description: Users have the ability to edit a shared MARC bibliographic record in quickMARC from a member tenant, as long as that user has permissions to edit in the central tenant. Once a shared MARC bib record is edited and the corresponding instance is updated, those changes are propagated to the other member tenants.

Changes/additions: Must have permissions to edit in the central tenant.

Known limitations: None.

Actions required: None.

Authority control (UXPROD-4278)

Description: As in non-ECS environments, MARC bibliographic records can be linked - now either via manual or automated processes - to MARC authority records. In an ECS environment, the following links can occur:

• Shared MARC bib to shared MARC authority

• Local MARC bib to shared MARC authority

• Local MARC bib to local MARC authority

Updates to shared MARC authority records will update the shared or local MARC bib records that appear in the member tenants.

Changes/additions: None.

Known limitations: None.

Actions required: None.

Identifying a record as shared or local in quickMARC (UXPROD-4265)

Description: In the quickMARC UI, and in the source view of the MARC bib record, users can identify whether the current record is shared or local depending on new headings and paneheader text.

Changes/additions: None.

Known limitations: None.

Actions required: None.