Page Comparison

...

• Convener and notes: Martina Schildt 
• Next meeting: 28 Jun 2023 - no meeting on 19 Jun 2023 
• Possible AI topic:

  Jira Legacy
  server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4343

Discussion items

1. Implementers topics | Cross-app: UX/UI
   1. Enhancements to the UI for Inventory/Quick Marc: UI Enhancement list - status of 2023 (Nolana) | Natascha Owens 
   Previous to do - open topic:

2. Open action items from former discussions

   1. MCL: export lists - complete list

      1. 
         

         is a Spike created?
      2. are there possible ways to export full MCL list to excel technically

Minutes

Enhancements to Inventory/Quick Marc

Drop down menu for statistical codes should be searchable (or jump to codes based on whatever characters user types into the box–type ahead?); This works in the search & filter pane in Inventory but not when trying to look up a statistical code when adding to Instance/Item/Holding.

• Locations work as required again
• should be implemented consistently
• is this working in other apps as expected?
• agreement: is an app by app decision → should be discussed in individuals SIGs
• for Inventory Natascha will create a ticket - Charlotte will support if needed

In edit mode, user should not be able to save a Receiving History entry if it is completely null (both enum and chron empty)

• is a bug - tickets need to be created for the different fields where this is possible - one ticket for each field should be sufficient → Natascha will create a ticket
• Laura in chat: I see we can do the same for holdings statments and electronic access
• it's the entire element that shouldn't be blank
• Maura in chat: Are there fields that should not have validation?  That should be permitted to be null?
  • fields that are already existing?
  • Owen in chat: I’d guess that in cases where you have the “add xxx thing” and that adds a field set to the form then it would be unusual for it to be OK for the whole fieldset to be null → agreed in the group

Would be preferable for Holdings notes to default to staff only (and we only have to uncheck the box when we want the note to display to the public, since most holdings notes are generally for staff only)

• is a feature request for Inventory
• in some libraries notes are rather internal, in other rather external → would be good to have a setting where this can be indicated
• sometimes even different locations would want a different default than others
• Laura in chat: is this the sort of issue that record templates might help with? (e.g., the template could have the staff only box checked)
• Martina S. in chat: In my opinion it would definitely be good to talk about areas where templates would make sense
• Laura in chat: there is work beginning on templates for quickMARC
• Natascha in chat: For serials, for the most part we are working with existing holdings records where we are adding notes, etc. so I'm not sure templates would help for every scenario
• Maura: do we need a template app? 
• would macros be a solution
• templates for field sets could be another solution - but there will be many
• Owen in chat: I’d say it’s probably more about each app implementing templating in the same/similar way rather than having a templating app - because the app already know how the data needs to be structured to populate the form

Ability to customize column data (and order of columns) included in item list

• being able to hide columns is alread possible in other places
• filtering for expected pieces is possible in Receiving
• To do: have a meeting with Gill, Kimie, Khalilah on sorting of columns, filtering etc.

Because trash cans are to the right of fields, they are far enough away from the field data to make it too easy to delete the wrong row--move trash cans to the left or add checkboxes instead?

• Skipped → UIQM-256 (DONE, with Nolana)

Delimiters in "View source" should display as $ as they do in quickMARC to make it easier to copy and paste data from View source into quickMARC

• Laura: asked for institutions to be able to choose delimiters
• should at least be the same
• Owen in chat: From LOC: Different software programs use different characters to represent the delimiter on the screen or on printouts. Examples are a double dagger (double dagger), an "at sign" (@), a dollar sign ($), an underline ( _ ), or the graphic symbol "delimiter symbol - 855 Bytes"
• Charlotte in chat: In Denmark the standard delimiter is an Asterisk: E.g. 001 00 *a [Postens ID-nummer] 004 00 *a e 008 00 *t m *a 1982 *z 1992 *l dan *v 0 009 00 *a a 010 00 *a DBF 011 00 *a [Hovedmaterialets posts ID-nummer] 245 00 *a Trafikmålinger i Storstrøms amt *y Tabeller
• this should be a tenant level setting → discuss in MM SIG
• Owen: additional approach: paste should always work - no matter the delimiter
• To Do: Laura will forward this topic and possible approaches to Khalilah

Postponed: Open action items

• MCL: export lists - complete list

  1. is a Spike created?
  2. are there possible ways to export full MCL list to excel technically

...

Minutes

Next steps

Chat

• further MCL agreements: UI / UX agreements across apps → if no tickets existing → Martina will create them

•  Clarify: is it technically possible to export full MCL list to excel Martina Schildt | possibly create a Spike if not yet existing

Next steps

Chat

18:02:33 Von  Martina Schildt | VZG  an  Alle:
    2023-06-14 Meeting notes: Implementers topics: UX/UI Inventory/QuickMarc
18:03:04 Von  Charlotte Whitt  an  Alle:
    One problem with virtual meetings are, that we tend to squeeze in many more meetings, than what would be possible to do in face-to-face meeting planning
18:03:16 Von  Jana Freytag  an  Alle:
    Reacted to "One problem with vir..." with 💯
18:03:21 Von  Maura Byrne  an  Alle:
    Reacted to "One problem with vir..." with 💯
18:03:39 Von  Charlotte Whitt  an  Alle:
    And that cause us to shift during a day through many, many different context and task
18:05:25 Von  Martina Schildt | VZG  an  Alle:
    Reacted to "One problem with vir..." with 💯
18:05:43 Von  Martina Schildt | VZG  an  Alle:
    So true
18:05:54 Von  Maura Byrne  an  Alle:
    Reacted to "So true" with 💯
18:07:37 Von  Owen Stephens  an  Alle:
    These sound like Inventory enhancements - I think the functionality is there but not applied. I don’t see a cross-app aspect to it in this case
18:11:32 Von  Laura Daniels  an  Alle:
    any of these elements that are customizable have the potential to end up with very long lists of values
18:11:43 Von  Maura Byrne  an  Alle:
    +1 Owen
18:11:50 Von  Ros, Amanda L  an  Alle:
    Reacted to "+1 Owen" with 💯
18:16:23 Von  Laura Daniels  an  Alle:
    I see we can do the same for holdings statments
18:16:44 Von  Laura Daniels  an  Alle:
    and electronic access
18:17:50 Von  Ros, Amanda L  an  Alle:
    Reacted to "One problem with vir..." with 💯
18:18:22 Von  Laura Daniels  an  Alle:
    right, Owen, it's the entire element that shouldn't be blank
18:20:30 Von  Maura Byrne  an  Alle:
    Are there fields that should not have validation?  That should be permitted to be null?
18:22:00 Von  Owen Stephens  an  Alle:
    I’d guess that in cases where you have the “add xxx thing” and that adds a field set to the form then it would be unusual for it to be OK for the whole fieldset to be null
18:22:25 Von  Maura Byrne  an  Alle:
    Reacted to "I’d guess that in ca..." with 👍
18:23:16 Von  Owen Stephens  an  Alle:
    I agree Laura that seems like a pretty likely rule
18:28:58 Von  Laura Daniels  an  Alle:
    you're right, Owen, I'm sure some of our locations would want a different default than others
18:29:12 Von  Heather McMillan  an  Alle:
    Yes - I am in the same library as Amanda, and most of the notes my dept adds need to NOT show to the public.
18:29:53 Von  Laura Daniels  an  Alle:
    is this the sort of issue that record templates might help with? (e.g., the template could have the staff only box checked)
18:31:01 Von  Martina Schildt | VZG  an  Alle:
    In my opinion it would definitely be good to talk about areas where templates would make sense
18:31:06 Von  Martina Schildt | VZG  an  Alle:
    Reacted to "is this the sort of ..." with 👍
18:31:11 Von  Ros, Amanda L  an  Alle:
    Reacted to "is this the sort of ..." with 💯
18:31:53 Von  Laura Daniels  an  Alle:
    there is work beginning on templates for quickMARC
18:33:44 Von  Martina Schildt | VZG  an  Alle:
    would it make sense to ask for Demos of how this is done in Orders and Quickmarc?
18:33:57 Von  Laura Daniels  an  Alle:
    Reacted to "would it make sense ..." with ➕
18:33:57 Von  Maura Byrne  an  Alle:
    Replying to "would it make sense ..."
    
    I’m in favor of this.
18:34:00 Von  Natascha Owens (UChicago)  an  Alle:
    For serials, for the most part we are working with existing holdings records where we are adding notes, etc. so I'm not sure templates would help for every scenario
18:34:09 Von  Ros, Amanda L  an  Alle:
    Replying to "would it make sense ..."
    
    demos are always a good idea
18:34:15 Von  Laura Daniels  an  Alle:
    Replying to "For serials, for the..."
    
    good point
18:34:20 Von  Martina Schildt | VZG  an  Alle:
    Reacted to "good point" with 👍
18:34:41 Von  Ros, Amanda L  an  Alle:
    Reacted to "would it make sense ..." with ➕
18:34:43 Von  Ros, Amanda L  an  Alle:
    Removed a ➕ reaction from "would it make sense ..."
18:34:51 Von  Heather McMillan  an  Alle:
    Reacted to "For serials, for the..." with 👍
18:39:00 Von  Owen Stephens  an  Alle:
    I’d say it’s probably more about each app implementing templating in the same/similar way rather than having a templating app - because the app already know how the data needs to be structured to populate the form
18:40:33 Von  Maura Byrne  an  Alle:
    Reacted to "I’d say it’s probabl..." with 👍
18:40:51 Von  Martina Schildt | VZG  an  Alle:
    Reacted to "I’d say it’s probabl..." with 👍
18:42:58 Von  Owen Stephens  an  Alle:
    Electronic holdings in inventory rather than eHoldings 🙂
18:54:48 Von  Owen Stephens  an  Alle:
    From LOC: Different software programs use different characters to represent the delimiter on the screen or on printouts. Examples are a double dagger (double dagger), an "at sign" (@), a dollar sign ($), an underline ( _ ), or the graphic symbol "delimiter symbol - 855 Bytes".
18:55:56 Von  Charlotte Whitt  an  Alle:
    In Denmark the standard delimiter is an Asterisk:
    E.g.
    001 00 *a [Postens ID-nummer]
    004 00 *a e
    008 00 *t m *a 1982 *z 1992 *l dan *v 0
    009 00 *a a
    010 00 *a DBF
    011 00 *a [Hovedmaterialets posts ID-nummer]
    245 00 *a Trafikmålinger i Storstrøms amt *y Tabeller
18:57:03 Von  Maura Byrne  an  Alle:
    +1 Charlotte
18:57:20 Von  Maura Byrne  an  Alle:
    That sounds like a tenant-level setting.
18:58:40 Von  Ros, Amanda L  an  Alle:
    I need to drop off
18:58:52 Von  Martina Schildt | VZG  an  Alle:
    Thanks
18:59:29 Von  Charlotte Whitt  an  Alle:
    I have to drop off too. Have a nice evening
19:00:10 Von  Martina Schildt | VZG  an  Alle:
    you too
19:01:17 Von  Maura Byrne  an  Alle:
    I have to go.  Thanks, everyone, for a good meeting.
19:02:27 Von  Owen Stephens  an  Alle:
    Ah - got it - it’s a request to /source-storage that gives back that source view

Attendees

...