Page Comparison

Charlotte Whitt Laura E Daniels 

Revisit UI/UX for Instance Mark for deleting. We presented the two ways to do Mark of instance deletion - either in the Edit form or in an Action menu, at the meeting on 30/6. We have since learned that it will be much easier. 

• We think it will be easier to do in Action menu, but unclear just yet. Should be able to move forward and more info to come to MM SIG.

Jenn Colt Laura E Daniels 

1.) Browse by series expectations (Nolana)

• Title data > Series statements
  • Marc mapping includes all except some control numbers - 4xx?, 8xx, all various subfields, all into one instance field.
    • Jacquie - Would like to see 490 when no 830 exists or just 830. Wouldn't want to see $w.
      • Reminder - can remove fields/subfields from default mapping if desired.
      • Only the 8xxs in the default MARC-Instance mapping
        
  • Is it acceptable for browse list to include all of the info in the Instance Series statement field?
    • Browse list is using the Instance series statement regardless of source.
    • Currently Inventory doesn't know if authorized.
    • What are the reasons staff are browsing by series?
      • Find all works that have series title in data
      • Find missing volumes
      • Spell checking
      • If classed together - wanting to check that they have been done consistently
    • Sounds like current information included in browse is useful for the above use cases.
      • Per chat: ISSN also needed.
      • If all is included, mapping could be used to remove information from Instance display.
      • For records that are not source MARC, how will you control browse info display?
    • Khalilah will proceed with building some more mock-ups and have group review.
      • Will need to figure out volume and sorting.

2.) Browse by genre/form handling (Orchid)

• Previously discussed - Interest in being able to identify genre/form in instance which would make browse easier
• Want to discuss at WolfCon - Discovery and FOLIO
• SIG and Felix Hemme should discuss
• Need to be sure to discuss in context of future with discovery based on Inventory model (not marc).
  • Anne-Marie: One concern I have is similar to what Jacquie is saying, but sort of opposite. I'm all for reconsidering and making things more granular if necessary, but each adjustment - especially to make things more granular - has substantial work, not only for development, but also for converting a library's existing Instance data to reflect the schema change
• MM SIG will discuss and work will move out to Orchid/Poppy depending on what is decided by group

3.) Proposed quickMARC UI changes

How to show field is now controlled by Authority record?

• Context
  • Hard to support in single text box, so current mock-up shows subfields pulled out as editable.
  • Feedback given around ability to tab across these subfields.
  • Is this a good way to convey what is editable and what is not? Show all subfields be in separate boxes to be consistent?
• Mock-up: All subfields in separate boxes. Option B
  
  • Will support tabbing through AND indicate what is controlled and what is not.
  • Could slow down staff entry? Fields with many subfields?
    • Will break into boxes once saved. You can add subfields in initial box (e.g. copy entire series of subfields and paste) and then once saved it will be broken up.
  • What about copying entire string to create new field?
    • Still needs to be figured out to allow for this.
  • Is tabbing across all seen as needed? In particular in light of other features that are needed?
  • Option could be to only apply to Controlled fields. Option A
    • Alot of consensus around this
    • Will still need to copy and paste entire field
• Option C
  
  • Nice to be able to tell at a glance
  • Would not want to get surprise error messages

Question: Will fields only be locked down if library has that Authority record in FOLIO also? YES, BUT if no automated linking enabled than the fields will be editable.

• • • Some institutions plan to
be able to tell at a glance
• Would not want to get surprise error messages

Question: Will fields only be locked down if library has that Authority record in FOLIO also? YES, BUT if no automated linking enabled than the fields will be editable.

• • • Some institutions plan to use the manual process and not rely on Automation. Is this written so that it can be used in the Entity Management app at some point?
    • Khalilah: Development must take into account Entity Management App. However it is developed, needs to consider catalog enrichment, linked data, entity management. Requirement is written as such.

Timeline for Authority linking:

• • • Nolana - Manual link capability, lock-down will be considered re: Data Import. Will not block updates, will report out. 
    Orchid - Automated linking
    • use the manual process and not rely on Automation. Is this written so that it can be used in the Entity Management app at some point?
    • Khalilah: Development must take into account Entity Management App. However it is developed, needs to consider catalog enrichment, linked data, entity management. Requirement is written as such.

Timeline for Authority linking:

• • • • Nolana - Manual link capability, lock-down will be considered re: Data Import. Will not block updates, will report out. 
      • Orchid - Automated linking.

Additional Updates from quickMARC group

• Make it easier to know selected field that is deleted
• Support deleting multiple fields with one action
• Able to tab from one subfield to another

Second iteration for Keyboard Shortcuts?

• Requires more of Khalilah's time or a PO.
• Complex across different keyboards. No pattern to rely on.
• Could it be a tenant localization? Or could tenants create their own shortcuts?
• Need to determine a path forward. Possibly at WolfCon.
  • Charlotte: We can use the need for a PO for Key board short cuts as an example at the PO session at WOLFcon, where we try to recruit new POs.

Slide deck -