You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 7
Next »
Attendees (please add your name):
Magda Zacharska leeda.adkins@duke.edu Jennifer Eustis (OLD ACCOUNT) Erin Nettifee Amanda Ros
Note Taker:
Robert Scheier
Meeting Recording:
Discussion:
| Topic | Details |
|---|
| Housekeeping | - Attendees - please add your name to the list of attendees
- Meeting host - please turn on Transcript option for the meeting
- Other topics?
|
Development updates | |
Item status In Progress (MODEXPW-348) | - Change to values supported in the Inventory UI (Missing and Withdraw)?
- Should it require additional permission?
|
| Bulk edit - user permissions (UXPROD-3468) | 1. What are the most common use cases for removing or adding permissions?
2. How permissions for the bulk edit should be identified: - User identifiers (barcodes, uuids, external system ids, usernames)
- User groups ?? (since they are not employers groups they might not be applicable)
- Permissions UUIDs (or should it be or permissions display name?)
3. What data should be presented in the matching records table: - Last name, first name, middle name, patron group?
- or permission display name?
4. Should the user be able to bulk edit , hidden and deprecated permissions? |
| Query tool (UXPROD-3785) | |
| Bulk Edit Use cases | Reviewed use cases and associated existing JIRA tickets or marked which ticket still needs a JIRA to be created. Follow up questions on: | Number | Use case | Notes |
|---|
| 29 | Add a similar feature to Sierra Global Update that allows you to see the data from the fields of the same type (author, subject, title, etc.) present in a set (review file) of records. Use case – Identify bib records from the daily headings reports that have not been sent for authorities processing. Example: Backstage inserts a code indicating that a bib record has been processed in the 040 field. I can view all the 040 fields from a set of records using the “toggle” function in Global Update and select records for future authorities processing. Use case – Find patterns of problems in a set of records. Example: During record loading, some MARC fields may end up being duplicated. Sierra Create List searching cannot find duplicate fields, but the “toggle” function in Global Update helps identify affected records. |
| | 30 | Ability to temporarily add or remove a MARC field in SRS. Use case – To temporarily exclude some bib records from authorities processing, we add a 9XX note and re-write the monthly search query to exclude records using that note. Example: The recent EEBO record load was huge, so we had to temporarily exclude them from the month’s authorities processing query. |
| | 36 | When the 3-part Item State is available/developed, there will be the need to identify item records based on a 1-part item state, location, etc. in order to update them with one or more of the 3-part states. This could be done based on a list of item records (HRIDs or Barcodes), or by location alone, depending on how the 1-part item state is used with location, or other data, at individual institutions. |
| | 49 | Ability to identify records with certain characteristics (a particular 650, for example) and permanently add a MARC field in SRS and Instance to those records. Use case: In-house record enhancements (adding new controlled vocabularies such as LCGFT or LCMPT) |
| | 57 | We want to be able to find and delete duplicate fields. We want to be able to specify the field or fields where we want to remove duplicate data. |
|
|