| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | THIS IS THE FINAL VERSION OF THE SPREADSHEET FOR THE 2022/2023 USE CASES SUB-GROUP, FOR NEW COMMENTS OR USE CASES, PLEASE USE THE WORKING COPY | ||||||||||||||||||||||||||||
2 | Related Jira(s) Entity Management Epic | Preliminary Priority Rank | Entity Management Use Case Description | Use Case details/additions | FOLIO Role(s) | Library/Type(s) Include original library type and additional when appropriate | Use Case Category | Comments/Discussion -- Please include initials and date, make comments in non-black for clarity and review | Date Use Case Added | ||||||||||||||||||||
3 | UC1 | Entity Management Epic MODLD-35 | R1 | As a metadata manager, I need tools, such as logs, that show changes, updates, deletes, non-matches between FOLIO descriptive metadata and external datasets for authorized access points so that I can maintain information between systems and datasets in order to maintain accurate authorities. | On a weekly basis, for example, I need to analyze when bibliographic records headings do not have a corresponding authority record match. Or when there are multiple potential matches. etc. This action should be able to be run on SRS or FOLIO descriptive records added or updated during a certain period. This work might be done with a 3rd party authority control vendor, internally with FOLIO systems, both, or with some system we haven't imagined yet. Triggers to have system check data points. Change on either side of the relationship (new bibs, updated bibs, updated authority, new authority) -- JS Duke Feb '23 | Metadata Manager Systems Administrator | Large academic National | Change Management/Authority Management Manage Local Data/Local Values | Are these tools within FOLIO? And are they surfacing changes in the external datasets (for the purpose of maintaining locally cached entities / data derived from the external data sets) or are they surfacing changes in local data that have relationships with entities from the external data set? Or both? (We want both!) CT - UChicago. | 11/20/2022 -- JS Duke | |||||||||||||||||||
4 | UC2 | MODLD-35 | R1 | As a cataloger, I want to view changes in non-MARC thesauri (or any external dataset) and update local MARC/BIBFRAME descriptions so that I can maintain accurate information between systems. | These data changes/additions should also be reflected in the logs of recently changed bib records. | Cataloger Metadata Manager | LC Large academic | Change Management/Authority Management Manage Local Data/Local Values | Add a note about how an institution defines what is triggered something manually (this use case) and the first (automated) . CT- Uchicago | 1/20/2023 -- JK LC | |||||||||||||||||||
5 | UC3 | UXPROD-4226 UXPROD-2524 | R1 | As cataloger, I want entity lookups to be incorporated into data input forms (cataloging forms) to previously identified datasets so that I can easily reuse existing descriptions (internal to FOLIO, along with external data sources/vocabularies). | 3 kinds of integrations we can think of: 1. locally cached dataset for authority look ups. (preferred for Entity App) 2. Sinopia Questioning Authority interface 3. Look up outside FOLIO, copy/paste (least preferred) LCNAF, LCSAF, LC geographic data, Getty Thesauri, etc. cross-searching with locally created/maintained data. In the Questioning Authority work, the PCC has identified the following vocabularies for looking up: https://docs.google.com/spreadsheets/d/1rPvEoP9iYNkxJ0eWC8gXe3ci7e6mhW0da59xkGhadi0/edit?usp=sharing "If we are selecting an authority we do need to know its source. Sometimes a preferred source is contextual." - Christie T. | Cataloger Metadata Manager | LC National Large academic | Resource Description / External entity lookup, import, and linking Support for Library Staff Discovery | Perhaps also a defined system for requesting new vocabularies? And to be able to choose locally which vocabularies appear in the form?NL-Stanford See Use Case 25 | 2020 | |||||||||||||||||||
6 | UC4 | MODLD-36 UXPROD-2520 | R1 | As a cataloger, I would like to create entities locally. | See UseCase 22 for work done prior to creating entities locally. Support for Library Staff Discovery use case | Cataloger | Large academic | Resource Description Manage Local Data/Local Values | 2020 | ||||||||||||||||||||
7 | UC5 | UXPROD-4280 UXPROD-4278 MODLD-37 | R1 | As a metadata manager or cataloger, I would like locally created entities to be shareable to external or internal systems including the FOLIO Entity lookup services, NACO/SACO funnel projects and utilities. | Exporting local authorities for the shared cataloging community needs to be possible for metadata managers. FOLIO community members may want to mint URIs in local namespaces, rather than simply sharing to external namespaces. | Cataloger Metadata Manager | Large academic | Resource Description Cross App Integration Support for emerging ontologies and data modeling Support for Library Patron Discovery | Would we want this local entity to have a URI or would we rely only on an internal connector ($9?) NL-Stanford Institutions are encouraged to maintain thier own namespaces whenever possible, the Missing Link (LOC) Dev team at Ebsco has stated that they will try to reduce the number of blank nodes overall. Strings will be possible as an object of a triple, but URIs are preferred in subject and predicates in entity definition. | 4/25/2023 - Use Case Group Discussion | |||||||||||||||||||
8 | UC6 | UXPROD-2522 | R2 | As a reference librarian, I need to search by MARC tag or BF element regardless of what format the element was created in so that I can answer a researcher’s inquiry. | This would be a different interface than that created for UC3, but should include data from multiple, identified vocabularies. Results should be drawn from both authority data and related bibliographic records, the reference librarian should be able to link from a list of results to specific bibliographic records. A management system should be used to determine what fields/elements should be included in "title" searches, as an example. Results from a title search should include information from previously identified fields and elements. | Catalog User | LC Large academic Any Library Type | Support for Library Staff Discovery Cross App Integration | 1/20/2023 -- JK LC | ||||||||||||||||||||
9 | UC7 | UXPROD-1646 | R1 | As a reference librarian, I need to search using non-Latin scripts (for example, Hebrew) to identify a BIBFRAME resource and answer a researcher’s inquiry. | Catalog User | LC | Support for Library Staff Discovery Cross App Integration | Is the assumption that there are multiple representations that would be in the entity records and that these scripts would all be available for searching or is this just a search UI requirement? CT - Chicago. Years ago, there was a proposal on alternate graphical representations in FOLIO, display of those, searching for them, etc.; this was rejected as a breaking change. We now need to reframe and re-propose solutions that allow better management and viewing of alternate graphical representations of languages. -- JS - Duke. Additionally, how can we take advantage of the linked data to find entities with data non-roman scripts outside our current authority management systems and entity records within FOLIO - aka Wikidata, VIAF, etc. - JS - Duke SF- Question, it sounds like this use case only requires the ability to enter search terms in Hebrew, not to support any filtering or special search modes. Is this correct? (If so, I have no concerns. Sounds like the need is for non-Latin scripts to be properly indexed and displayed, and that literals don't always have to have language tags.) | 1/20/2023 -- JK LC | ||||||||||||||||||||
10 | UC8 | UXPROD-4226 UXPROD-2524 | R1 | As a cataloger, I want to use a lookup service to identify entities (names, subjects, etc.), outside my local system to cache locally. Including authority records in LCNAF or LCSH for examples, so that I can add to FOLIO to enhance my work. | This use case expands/enhances UC3. | Cataloger | Small academic Large Academic LC | Support for Library Staff Discovery Cross App Integration External entity lookup, import, and linking (Extensible Modeling and 3rd-party lookups) | Is this about cacheing / storing all or parts of entity records from external sources locally and selecting them record by record or about selecting an external source and then making it available in part or as a whole within FOLIO to support linking, reporting, and maintenance? If the second this might also be large academic. CT_Uchicago. Link to Origanal WGs dataflow diagram. | 1/20/2023 -- JK LC | |||||||||||||||||||
11 | UC9 | R2 | As a metadata manager, I want to view updates from entity record sources (id.loc.gov LC Name Authority, or the Getty Thesauri, for examples) and apply them to my local resource descriptions to keep our catalog accurate and up to date. Other linked entities identified by the institution should also be viewable. | Three Features for this use case can be imagined: See also UC10 and UC11. | Metadata Manager | Large academic Small academic LC | Manage Local Data/Local Values Change Management/Authority Management | Reports or logs? Automated application or manual application? - CT UChicago | 1/20/2023 -- JK LC | ||||||||||||||||||||
12 | UC10 | UXPROD-2517 | R3 | Parse changes in data sources, perhaps via Activity Streams, update cache, create reports for changes needed in bibliographic descriptions, automatically change (and provide a report for) headings that are safe to automate. | Metadata Manager | Large academic Small academic | Change Management/Authority Management Support for emerging ontologies and data modeling | 3/7/2023 - Use Cases Group | |||||||||||||||||||||
13 | UC11 | UXPROD-2523 | R2 | Using reports of changes to source data, allow the user to conduct manual updates to authorities, authorized headings, and other bibliographic data | Use dashboards (in Entity Management App) to utilize pre-existing searches to ID records and elements which require maintenance. Allow the cataloger to view information where one heading is replaced by 2 or more, for example. | Metadata Manager | Large academic Small academic | Resource Description Change Management/Authority Management | 3/7/2023 - Use Cases Group | ||||||||||||||||||||
14 | UC12 | UXPROD-2863 | R1 | As a metadata manager, it is important that I can track of record creation provenance for staff and workflows. For troubleshooting and QC, it would be useful to be able to include context for the work; i.e.: Batch Update, by XXX, on YYY date. | This type of productivity measurement is not allowed in some countries. However, for training and QC needs, provenance can be useful for managers. See also UC33 | Metadata Manager | Large academic Small academic LC | Manage Local Data/Local Values Cross App Integration Change Management/Authority Management | Christie: Is there versioning for authority / entity records the same way there is for Inventory records? Christie can demo how this works in FOLIO to see if it is a possible solution. | 1/20/2023 -- JK LC | |||||||||||||||||||
15 | UC13 | MODLD-39 | R1 | Import single entity records from MARC, and other data sources | Also, overlaying a single entity record | Metadata Manager Cataloger | Large academic Small academic | Resource Description Change Management/Authority Management | 3/7/2023 - Use Cases Group | ||||||||||||||||||||
16 | UC14 | MODLD-28 | R1 | As a cataloger, I need to be able to create, edit and deprecate BF entities such as works, subjects, places, and agents. | May need to also create other entity types. Deletions - when can a resource be deleted forever vs made inactive? | Cataloger | LC Large academic Small academic | Resource Description Manage Local Data/Local Values Cross App Integration Change Management/Authority Management | Right now in FOLIO we have implemented Optimistic locking. Christie added that people should always be able to have the backup option of deleting. This usecase also relates to usecase #4 CT - Is this only applicable to bibframe entities? Same question applies to other references to BF entities. | 1/20/2023 -- JK LC -- from LC FOLIO | |||||||||||||||||||
17 | UC15 | MODLD-28 | R1 | As a cataloger, I need to be able to create, edit and delete links between BF works, instances, subjects, agents, etc. including links to files external to the institution | Facetted linking for subject heading components. This is possible in LC's Marva editor. Linking at the heading level and linking to the components as well. This can be considered a type of edit as described in UC14. | Cataloger | LC Large academic Small academic | Resource Description Manage Local Data/Local Values Cross App Integration Change Management/Authority Management | 1/20/2023 -- JK LC -- from LC FOLIO | ||||||||||||||||||||
18 | UC16 | R2 | As a cataloger, I need to be able to copy/clone/derive new descriptions for entities from internal existing descriptions, either one-by-one or as a batch process. | The typical copy-cataloguing process, where we're creating a new description for a new resource, avoiding starting from a blank form. Also present when re-using Shared-VDE data. Avoid to create copies, which get out of sync with the source. If creating a new description of the same entity, consider adding an "equivalency" statement linking to the previous description. See also UC21. | Cataloger | LC Large academic Small academic | Resource Description Manage Local Data/Local Values Cross App Integration Change Management/Authority Management | Current Marva functionality can be used as a baseline for development. | 1/20/2023 -- JK LC -- from LC FOLIO | ||||||||||||||||||||
19 | UC17 | UXPROD-4286 | R1 | As a cataloger, I need to be able to validate descriptions (authority records) as conforming to a specification, standard or application profile. | Validate against misc. sources; e.g. .... settings to validate shapes / groups of properties and classes - SHACL can be an option but TBD if that meets all LC needs. Configuration tools to define validation rules to be applied in the workflow is needed. Entity App Configurations should be shareable and digestible to/from other FOLIO institutions. | Cataloger | LC Large academic Small academic Multi-tenant consortium | Cross App Integration Resource Description Change Management/Authority Management | 1/20/2023 -- JK LC -- from LC FOLIO | ||||||||||||||||||||
20 | UC18 | R2 | As a cataloger, I need to be able to perform batch editing of descriptive data, including the ability to view changes in a sandbox environment before they are committed. | This can be both bulk edit or update of a group of data. Sandbox or preview mode. | Cataloger Metadata Manager | LC Large academic Small academic | Cross App Integration Resource description Change Management/Authority Management | Will check if the current work on Bulk edit has preview functionality. Would like to have UX consistency. Will check with the PO for Bulk edit. | 1/20/2023 -- JK LC -- from LC FOLIO | ||||||||||||||||||||
21 | UC19 | MODLD-39 | R1 | As a cataloger, I need to be able to reuse descriptions from external sources (vendors, PCC, other institutions, cloned/derived from other descriptions) | Preferred labels, variant labels, etc.,may need to be developed. Similar to UC16, but external descriptions | Cataloger Metadata Manager | LC Large academic Small academic | Resource Description Manage Local Data/Local Values Cross App Integration Change Management/Authority Management | 1/20/2023 -- JK LC -- from LC FOLIO | ||||||||||||||||||||
22 | UC20 | R1 | As a cataloger, I need to be able to use dynamic lookup within the metadata editor to find and select correct terms for which to create links. This should also support lookup of files external to LC. | See UC3 and UC4 | Cataloger | LC | External entity lookup, import, and linking Resource Description | 1/20/2023 -- JK LC -- from LC FOLIO | |||||||||||||||||||||
23 | UC21 | R1 | As a cataloger, I need to be able to validate controllable terms in a description (when reusing data with existing terms, for example) and suggest appropriate links; one step further, I wish I don’t need to do the validation process for the controlled/authority terms that have been validated. I can directly pull the terms without worrying about typos | This use case is an extension of UC3, providing insight into expected behaviors once a entity is found in a lookup. (use for: Control the Heading) This would also be useful when cloning/coping a bibliographic record, UC16. | Cataloger | LC Large academic | Resource Description External entity lookup, import, and linking Support for Library Staff Discovery | 1/20/2023 -- JK LC -- from LC FOLIO | |||||||||||||||||||||
24 | UC22 | UXPROD-4282 | R1 | As a metadata manager, I need to ensure that catalogers' authenticated records created within a cooperative framework (CONSER, NACO, etc) are distributed to the appropriate places (OCLC, Cataloging Distribution Service, etc) | The ability to ID records new or updated in a specific range to export those in such a way that those can beput into distribution services. Where will LCCN (010) identifiers be minted? Also related to UC4 and UC5. | Metadata Manager | LC Large academic National libraries | Cross App Integration | Beyond the need to authenticate, is this about the ability to push to/write directly to an external store? Or will the external source pull from known sources? How do NACO libraries contribute to the NAF in an LD environment? Ask Andreas Mace, National Library of Sweden | 1/20/2023 -- JK LC -- from LC FOLIO | |||||||||||||||||||
25 | UC23 | MODLD-38 | R1 | As a cataloger, I need to be able to effectively search and browse existing data (internal and external) from within the Entity Management App so that informed decisions on data needs can be made (e.g.: edit, create, delete, etc.). | Broader than lookup UC3 and UC4. A search UI for entities within the App to determine that the entity sought is or is not already described. Management of Entities for data quality also required this kind of search/browse UI | Cataloger Metadata Manager | LC Large Academic | Support for Library Staff Discovery Resource Description | 1/20/2023 -- JK LC -- from LC FOLIO | ||||||||||||||||||||
26 | UC25 | MODLD-31 | R1 | As a cataloger, I want to be able to copy/paste text from other sources on the web as search terms for the catalog in non-latin scripts, precomposed or decomposed Unicode. We need to be able to paste any search term into the Entities App to discover entities, across the Entity record (e.g. 1xx, 4xx, 5xx terms in the result) | Unicode searching (regardless of composition) is a FOLIO-wide concern. This should be an early development concern so that the Alternate Graphical Representation proposal can be fulfilled where searching bibliographic data for one form of an entity results in displays of authorized entities based on their presence in the Entities App. | Cataloger | LC Large academic | Resource Description Support for Library Staff Discovery | This question brings to mind the Alternate Graphical Representation proposal. We would like to k | 1/20/2023 -- JK LC -- from LC FOLIO | |||||||||||||||||||
27 | UC26 | R1 | Each application connected to the Entity App will need to make processing (indexing and display) decisions, that includes variants labels (including non-latin). e.g. Results from an Inventory search should include results that match Entity data when relationships exist. | Sometimes the equivilent, graphically different forms of an entity will not be present in the bibliographic data, but the Entity app will contain such data. | System Integration | LC Large Academic | Cross App Integration Support for Library Staff Discovery | ||||||||||||||||||||||
28 | UC27 | UX-PROD 1646 | R1 | FOLIO architecture needs to support multiple labels for an entity, including multiple graphical representations of an entity name. These should be considered as equivilent forms of the entity. | Names/labels are core to UC26. | Large Academic | Cross App Integration Support for Library Staff Discovery | ||||||||||||||||||||||
29 | UC28 | R1 | As a cataloger, I want to be able to search the entity lookup service from data forms and be able to see the following information for selection: source, entity types (names v subjects), or whether it is a heading or a cross-reference in order to make the appropriate selection and populate the cataloging form, either by copying the entity ID, or selecting the data from the lookup results. | See UC3. Can the staff member be "sent" to a search UI to perform these sophisticated search and filter activities UC26 also covers display needs for selection. | Cataloger | Large Academic | External entity lookup, import, and linking | ||||||||||||||||||||||
30 | UC29 | R2 | After searching in the Entities app (see UC2), the cataloger should be able to use the data found in the cataloging form where the entity search began. This is, once the search is complete, the user should be taken back to the record being created/updated in Inventory or QuickMARC, etc. See also UC3. | Cataloger | Large Academic | Cross App Integration | |||||||||||||||||||||||
31 | UC30 | R1 | The result set should be able to be refined by filtering on source, heading type (names vs subject) and whether the entity found is in a heading or cross-reference field. | If the search is to see if a description already exists before creating a new description, see UC23. | Cataloger System integration | Any Library Type | Cross App Integration Support for Library Staff Discovery | ||||||||||||||||||||||
32 | UC31 | R1 | As a metadata manager/system admin, I want to select what information is populated in the data form when a term is selected via the entity look up service to prevent errors in relationship creation. (Settings) | See UC3. Bibliographic records should be populated with authorized Entity data, but not necessarily former headings, scope notes, etc. to prevent errors. The ability to configure the authorized heading is important because each thesauri may not be formatted in the same way, preferred terms may be modelled differently, so setting each authority type separately is needed. | Metadata manager System administrator | Large Academic | External entity lookup, import, and linking | ||||||||||||||||||||||
33 | UC32 | UXPROD-4278 UXPROD-4082 | R1 | As a manager of a multi-tenant consortium I want a convenient mechanism to manage authorities where each tenant's authorities data is updated "regularly". Extracting authority data from the tenants SRS authority data and sending as one file to a vendor should be possible, as well as updating the returned file simply so that I can maintain the accuracy and currency of authority data for my consortium. | The Entity management should be able to interact with a consortium app. Extraction and reloading would also be applicable to libraries/consortia that do this work locally. | System Administrator Metadata manager | Multi-tenant consortium | Cross App Integration Change Management/Authority Management | Will the connsoritum app (see mod-consortia) be able to interact with an Entity App? Will consortial members share data stores (they don't now)? | 03/28/2023 -- Lloyd from Marmot Library Network | |||||||||||||||||||
34 | UC33 | UXPROD-2863 | R2 | As a metadata manager/system admin/cataloger, I need to know who created or updated the record, when it was created and updated, etc. Including all versions of the record over time. | versioning and associated administrative metadata See also UC12. | Metadata manager System administrator | Cross App Integration Manage Local Data/Local Values | EMWG Use Cases discussion | |||||||||||||||||||||
35 | UC34 | R2 | As a metadata manager from the Entities App, I want to be able to see (and click to) which bibliographic records are linked to a particular entity, so that I can understand its usage in our catalog. | Similar to the log data shown in DI, where a job profile displays (and links to in Poppy) the results of the job. | Metadata manager System administrator | Large Academic | Cross App Integration Manage Local Data/Local Values | EMWG Use Cases discussion | |||||||||||||||||||||
36 | UC35 | R2 | As a metadata manager, I need to be able to rollback to a previous version of a record to ensure data quality is desired. The ability to rollback up to 5 previous versions of a record would enable me to ensure data quality. | Metadata manager System administrator | Cross App Integration Manage Local Data/Local Values Change Management/Authority Management | EMWG Use Cases discussion | |||||||||||||||||||||||
37 | UC36 | R1 | As a metadata manager/system admin, I need to identify, set up, and manage data from an external data set to act on those data in batches; including create new, update existing, deprecate and delete entities from local store / index. See UC1 | Institution settings, configurations, etc., to define the use of external datasets in FOLIO. Work done at initial ingest, could be edited/updated at a later phase in production. | Metadata manager System administrator | Large Academic | Cross App Integration Manage Local Data/Local Values Change Management/Authority Management | 4/11/2023 - CT/ UChicago | |||||||||||||||||||||
38 | UC37 | R2 | As a cataloger I need to add local notes to a locally cached version of an entity from an external data set. Local notes should not be overwritten when locally cached version is refreshed against the external data sets. | Presumes a cached form of the entity record where local notes could be stored, similar to Administrative metadata in the Instance, which persists when record is overlaid, etc. These data would not become part of the "canonical" entity record outside FOLIO. "local notes" | Cataloger | Large Academic | Manage Local Data/Local Values Change Management/Authority Management | Christie will check with UChic staff to confirm that these local notes are for, or not for, the discovery layer outside FOLIO. | 4/11/2023 - CT/ UChicago | ||||||||||||||||||||
39 | UC38 | R1 | As a cataloger I need to change a relationship (relink) a heading to an entity record. | Changes could come from within Entities or from within Instances Apps See also UC15 | Cataloger | Large Academic | Cross App Integration Resource Description | 4/11/2023 - CT/ UChicago | |||||||||||||||||||||
40 | UC39 | R2 | As a cataloger I need to establish relationships between a single heading and multiple entities from different external data sources. This data can be used, for example, in building knowledge cards in the discovery layers. | Creating equivilency, or near equivilency across thesauri would aid in resource discovery for our patrons | Cataloger | Large Academic | Manage Local Data/Local Values Change Management/Authority Management Support for Library Patron Discovery | 4/11/2023 - CT/ UChicago | |||||||||||||||||||||
41 | UC40 | R3 | As a cataloger I need to establish relationships between the component parts of a heading / access point and an entity when an entity that represents the heading in its entirety is not available. | Precoordintated headings give catalogers great flexibility in description, but cause difficulties in string management. Subheading maintenance is needed to maintain data integrity. | Cataloger | Large Academic | Resource Description Change Management/Authority Management Cross App Integration | 4/11/2023 - CT/ UChicago | |||||||||||||||||||||
42 | UC41 | R1 | As a cataloger I need to be able to click through to a linked entity record from a FOLIO Inventory, View Source, or QuickMarc record in order to confirm an accurate relationship has been made | Cataloger | Large Academic | Cross App Integration Resource Description | 4/11/2023 - CT/ UChicago | ||||||||||||||||||||||
43 | UC42 | R1 | As a metadata manager / system admin I need to trigger automatic updates of headings when defined changes are made to a linked entity record. See UC1 and UC32. After viewing, acting on those changes is needed, based on configurations. | These need to be configurable so that institutions can see what automations would do to their data. | Metadata manager System administrator | Large Academic | Cross App Integration Support for emerging ontologies and data modeling | 4/11/2023 - CT/ UChicago | |||||||||||||||||||||
44 | UC43 | R1 | As a system administrator, I need to be able to put local policies in place through configurations and settings. | For example, see UC36 | System Administrator Metadata manager | Large Academic | Cross App Integration | 4/18 - UC Group discussion | |||||||||||||||||||||
45 | UC44 | R1 | As a cataloger I want to manage headings / access points that do not have a linked external entity or authority record, or should have an underlying local entity record created. This could be implemented at the institution-level as a policy or configuration. | In a previous system every access point in a record where the headings could be controlled or linked to an entity / authority record generated a local entity record. I am not sure if this an ideal approach and it would require the ability to separate headings and merge them with an external data set if a record i identified or created in an external source. | Cataloger System administrator Metadata manager | Large Academic | Support for Library Staff Discovery Cross App Integration Change Management/Authority Management | This could be an intitutional setting where some libraries choose to have all headings are controlled. | 4/11/2023 - CT/ UChicago | ||||||||||||||||||||
46 | UC45 | R1 | Given that incorrect entity metadata has been found, as a metadata manager, I need to find all the bibliographic records which include that incorrect data, unlink it from bibliographic records, and potentially replace it with a correct entity or entities | An entity record needs to be merged or replaced with the correct entity record links | Metadata manager | Large Academic | Change management/Authority management | ||||||||||||||||||||||
47 | UC46 | R2 | As a metadata manager, I would like to expose equivilency relationships between entites encoded in multiple external thesauri within the local cached version, for example, of an entity record. Creating different types of relationships within the Entity, for example, with their ORCID IDs, and WikiData entries. | For use in Knowledge cards to improve patron understanding of entities, for example. Leveraging API tools to create on the fly these type of relationships is very interesting, as well. New techologies and AI may make entity relationship building more possible and automation. The act of creating the link should often happen within one or the other datasets (not locally), but how we expose/leverage the relationships locally should be considered. | Metadata manager | Large Academic | Support for Library Staff Discovery Support for Library Patron Discovery | Christie highlighted the need to export data for end users, for example in knowledge panels. One example query is "give me all the data about a person and all their mapped identifiers including LCNAF, Wikidata ID, and ORCID" | 4/11/2023 - JS/Duke | ||||||||||||||||||||
48 | UC47 | R1 | Subfield 0s imported with records from OCLC, vendors, etc. need to be retained at the field and subfield level. | Metadata manager Cataloger System Administrator | Large Academic LC National Library Multi-tenant consortium | Support for Library Staff Discovery Support for Library Patron Discovery | |||||||||||||||||||||||
49 | UC48 | R! | System configuration for entity record template. Shareable configurations are necessary. | Metadata manager System administrator | Change management | ||||||||||||||||||||||||
50 | |||||||||||||||||||||||||||||
51 | The following Use Cases were considered by the Use Case subgroup and were determined to be important, but should not be confined to the Entities App in FOLIO | ||||||||||||||||||||||||||||
52 | Wider FOLIO Use Case | As a cataloger, I need a place to save incomplete work so that I can pick it up to finish at a later date, or pass on to another colleague. | Allow something to be assigned/flagged for someone elses attention (to work on or review/approve). | Cataloger | LC | Resource Description Cross App Integration | This sounds like it should be part of a Workflow management system and should be incorporated into discussions around a Workflow app. Instance States, tags, and notes are also potentionally part of a workflow app, where provisional records, training review processes, etc. | 1/20/2023 -- JK LC -- from LC FOLIO | |||||||||||||||||||||
53 | Wider FOLIO Use Case | As a cataloger, I want to not have to modify or change my UI to access, catalog, amend MARC and BF records | Permissions around access to customizations is needed | Cataloger | LC | UI Customization | 1/20/2023 -- JK LC -- from LC FOLIO | ||||||||||||||||||||||
54 | Wider FOLIO Use Case | As a cataloger, it's important to not need to open multiple apps or windows so that I don't lose track of my work | Permissions around access to customizations is needed | Cataloger | LC | UI Customization | 1/20/2023 -- JK LC -- from LC FOLIO | ||||||||||||||||||||||
55 | Wider FOLIO Use Case | As a cataloger, I need to be able to use dynamic lookup within the metadata editor to find and select correct terms for which to create links. This should also support lookup of files external to LC. | SF - is this the same as UC3? | Cataloger | LC | See Use Cases #3 and #4 | 1/20/2023 -- JK LC -- from LC FOLIO | ||||||||||||||||||||||
56 | |||||||||||||||||||||||||||||
57 | |||||||||||||||||||||||||||||
58 | |||||||||||||||||||||||||||||
59 | |||||||||||||||||||||||||||||
60 | |||||||||||||||||||||||||||||
61 | |||||||||||||||||||||||||||||
62 | |||||||||||||||||||||||||||||
63 | |||||||||||||||||||||||||||||
64 | |||||||||||||||||||||||||||||
65 | |||||||||||||||||||||||||||||
66 | |||||||||||||||||||||||||||||
67 | |||||||||||||||||||||||||||||
68 | |||||||||||||||||||||||||||||
69 | |||||||||||||||||||||||||||||
70 | |||||||||||||||||||||||||||||
71 | |||||||||||||||||||||||||||||
72 | |||||||||||||||||||||||||||||
73 | |||||||||||||||||||||||||||||
74 | |||||||||||||||||||||||||||||
75 | |||||||||||||||||||||||||||||
76 | |||||||||||||||||||||||||||||
77 | |||||||||||||||||||||||||||||
78 | |||||||||||||||||||||||||||||
79 | |||||||||||||||||||||||||||||
80 | |||||||||||||||||||||||||||||
81 | |||||||||||||||||||||||||||||
82 | |||||||||||||||||||||||||||||
83 | |||||||||||||||||||||||||||||
84 | |||||||||||||||||||||||||||||
85 | |||||||||||||||||||||||||||||
86 | |||||||||||||||||||||||||||||
87 | |||||||||||||||||||||||||||||
88 | |||||||||||||||||||||||||||||
89 | |||||||||||||||||||||||||||||
90 | |||||||||||||||||||||||||||||
91 | |||||||||||||||||||||||||||||
92 | |||||||||||||||||||||||||||||
93 | |||||||||||||||||||||||||||||
94 | |||||||||||||||||||||||||||||
95 | |||||||||||||||||||||||||||||
96 | |||||||||||||||||||||||||||||
97 | |||||||||||||||||||||||||||||
98 | |||||||||||||||||||||||||||||
99 | |||||||||||||||||||||||||||||
100 |