Attendees (please add your name):
Magda Zacharska Jennifer Eustis Thomas Trutt Robert Scheier Sara Riggs Kimie Kester Lynne Fors Scott Perry
Note Taker:
Meeting Recording:
...
| Topic | Notes | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Housekeeping
| Notes: Jennifer Eustis | ||||||||||||
| 2 | Quesnelia release update |
| ||||||||||||
| 3 | Bulk edit - Staff only notes |
| ||||||||||||
| 4 | Bulk edit - MARC Instances |
Mockups: MARC Instances:
See Kimi's mockups in link above. The change in Action menu. If you have a source=MARC instance, there are still fields in the instance that you want to change. The proposal is to change to Instance fields and MARC fields. (Approved). For MARC fields, empty fields are indicated by \. Question: Noticed in Data Import that blanks are a blank space instead of \. This is inconsistent with Bulk Edit and QuickMarc. Magda will contact Ryan Taylor about this. The info icon provides information on the fields that this is limited to. Right now this is limited to 5XX and 9XX. Magda will put a survey in Slack to make sure we are getting all the priority use cases. For the Add action, there is an additional action to add more subfields. When clicked, you have another row to add additional subfields. Question: When you add a subfield, should the indicators be grayed out as well? This is a good point since the only action is adding a subfield and not changing the indicators. Or should we hide the boxes for the indicators with the add subfield? Yes. This is definitely what we want. If we change the indicators, then we want a new field. For the Find action, we have Append, Remove field, Remove Subfield, Replace. To remove a string, this is covered in the replace since you replace with nothing. Question: If there is only 1 of these fields and subfields, if you remove the field then you have an empty field. Would the action also remove the field since an empty field has no value? This will depend on validation rules and using the same ones with quickMarc. The validation rules would trigger an error and in this case it would not allow to save. For append, right now it's add at the end. It would be nice to be able to add at the beginning or end. Append is adding a subfield. To work with the content, you would then add a change with replace. FOLIO Instances:
Because of the number of fields, there is a search option to avoid scrolling through the options. For staff only, there is a checkbox. What if you have notes that are staff only and they need to be public, how do you do that? There would need to be a new option. For suppress from discovery, there are the additional options to apply to all holdings and items. For In, if this is an OR, then looking for records that have either of the stat codes. The "in" and "contains" are confusing. Boolean operators are easier to understand. See examples of operators and behavior. Decisions:
| ||||||||||||
| 5 | Bulk edit queries - follow up from Slack chat | Search by statistical code. You can see this in folio snapshot. It is common that records have multiple statistical codes. The "contains" will search for any records with these values. Should we use "In" rather than "contains"? +1. The boolean is easier to understand. "Contains" is a little confusing. Could we use "contains (OR logic)"? Why not just put a drop down between the codes for and or not? How many operators are allowed? There's no limit right now. | ||||||||||||
| 6 | Bulk Edit - in app approach - statistical codes - (UXPROD-3714) |
|
...