-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Open
Labels
Affects: LibrariansIssues related to features that librarians particularly need. [managed]Issues related to features that librarians particularly need. [managed]Lead: @horncIssues overseen by Charles (Staff: Data Engineering Lead) [managed]Issues overseen by Charles (Staff: Data Engineering Lead) [managed]Needs: BreakdownThis big issue needs a checklist or subissues to describe a breakdown of work. [managed]This big issue needs a checklist or subissues to describe a breakdown of work. [managed]Priority: 3Issues that we can consider at our leisure. [managed]Issues that we can consider at our leisure. [managed]Type: Feature RequestIssue describes a feature or enhancement we'd like to implement. [managed]Issue describes a feature or enhancement we'd like to implement. [managed]
Description
Feature Request
Problem / Opportunity
This commit hid the ocaid value based on availability results:
278fd34
As a Librarian checking and following the metadata is important, so it'd be helpful to still see the identifiers in the UI, at least for that usergroup.
Motivation: I modified the linked archive.org identifier for this item: https://openlibrary.org/books/OL6724732M/Thyroxine
from a printdisabled to an open edition (1929, public domain), and the identifier still didn't show up under Edition Identifiers as I expected. Is this a bug, or just the availability API being slow to catch up through cached values?
Proposal
Breakdown
Related files
Refer to this map of common Endpoints:
*
Requirements Checklist
Checklist of requirements that need to be satisfied in order for this issue to be closed:
- [ ]
Stakeholders
Instructions for Contributors
- Before creating a new branch or pushing up changes to a PR, please first run these commands to ensure your repository is up to date, as the pre-commit bot may add commits to your PRs upstream.
tfmorrisCopilot
Metadata
Metadata
Assignees
Labels
Affects: LibrariansIssues related to features that librarians particularly need. [managed]Issues related to features that librarians particularly need. [managed]Lead: @horncIssues overseen by Charles (Staff: Data Engineering Lead) [managed]Issues overseen by Charles (Staff: Data Engineering Lead) [managed]Needs: BreakdownThis big issue needs a checklist or subissues to describe a breakdown of work. [managed]This big issue needs a checklist or subissues to describe a breakdown of work. [managed]Priority: 3Issues that we can consider at our leisure. [managed]Issues that we can consider at our leisure. [managed]Type: Feature RequestIssue describes a feature or enhancement we'd like to implement. [managed]Issue describes a feature or enhancement we'd like to implement. [managed]