-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Open
Labels
Affects: UIIssues with the web site's user interface. [managed]Issues with the web site's user interface. [managed]Lead: @cdriniIssues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed]Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed]Module: WikidataNeeds: HelpIssues, typically substantial ones, that need a dedicated developer to take them on. [managed]Issues, typically substantial ones, that need a dedicated developer to take them on. [managed]Priority: 3Issues that we can consider at our leisure. [managed]Issues that we can consider at our leisure. [managed]Theme: IdentifiersIssues related to ISBN's or other identifiers in metadata. [managed]Issues related to ISBN's or other identifiers in metadata. [managed]Type: EpicA feature or refactor that is big enough to require subissues. [managed]A feature or refactor that is big enough to require subissues. [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
Any place that the user is asked to enter an identifier for which OpenLibrary has a URL template, they should be allowed to paste the full URL and have the identifier extracted from it.
UI Changes:
- Authors
- Good first candidate because it's already written in Vue
- Editions
- Identifiers
- "What work is this an edition of?" field should accept URL. Edit: It already does! :)
- Works
- IDs blocked by Add UI for adding work IDs #3430
- The author autocomplete field on the work edit. Edit: It can do this now
Next Steps:
- Setup Author Identifiers component to accept url match patterns (client side only)
- Create a mapping between our identifiers and Wikidata Identifiers (spreadsheet first, then code)
- Setup Wikidata integration to access Properties (currently only pulls QIDs)
- Plan/implement for how we'll load the url match patterns into Identifiers.
- I would propose we have an endpoint that aggregates them that the edit pages can call on load. But not cached too aggressively so we if people update patterns in Wikidata they get the changes fairly fast.
- Start using url match patterns in Authors, Editions, Works etc.
We should use the URL Match Pattern from Wikidata instead of maintaining it ourselves. See https://www.wikidata.org/wiki/Property:P214 for an example.
If we do that this is blocked by: #8236
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Affects: UIIssues with the web site's user interface. [managed]Issues with the web site's user interface. [managed]Lead: @cdriniIssues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed]Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed]Module: WikidataNeeds: HelpIssues, typically substantial ones, that need a dedicated developer to take them on. [managed]Issues, typically substantial ones, that need a dedicated developer to take them on. [managed]Priority: 3Issues that we can consider at our leisure. [managed]Issues that we can consider at our leisure. [managed]Theme: IdentifiersIssues related to ISBN's or other identifiers in metadata. [managed]Issues related to ISBN's or other identifiers in metadata. [managed]Type: EpicA feature or refactor that is big enough to require subissues. [managed]A feature or refactor that is big enough to require subissues. [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]