Page Comparison

UXPROD-1634 Inventory. Result list Refined display rules - establish small working group which to define short term improvements. 

UXPROD-1730 Inventory. Result list. Display elements should be configurable - long term solution.

Volunteers to address these Jiras in a smaller group are needed. Please contact Charlotte if you are interested.

Agenda/Notes

• All SIG conveners gave updates in this week's meeting.
• Discussion concerning reports and privacy requirements. Reporting needs a way to make sure they are able to identify information to identify information as "private". The POs to start will be asked to identify data elements that need to be anonymized or deleted.
• Third party possibility to do a VPAT - Voluntary Product Accessibility Template - an accessibility report that demonstrates what works well in terms of accessibility and brings to light improvements needed.
• Rankings will be converted to a new system of 1 to 5. Current rankings will be converted, but institutions may want to check their rankings in new system to make sure they are still in line with what they want.
• Prioritizing Fiscal Year Roll-Over
• Naming releases in tech council update. 

Review of proposed solutions:

• Model 1 - Shared item linked to multiple holdings records
• Model 2 - Primary/dependent items
• Model 3 - Super item

Which would work best for all (most?) scenarios?

A document to help summarize/frame the conversation

In all cases, it is important that item level data is accurate when it is viewed. 

• German libraries need an instance to instance relationship.
• Jacquie commented that the instance to instance relationship is not sufficient for some cases. 
• Chat comment: "Agree with Jackie. Her example can refer to issues of serials bound with monographic items, and with the situation I sent to Laura earlier where we had three copies of a particular pamphlet in three different bound-withs."
• Natascha - Hesitant about 1st model for analytics cases.
• Jacquie expresses concerned that parallel enumeration would not be possible in Model 1. Model 1 is not flexible enough.
• Laura feels that Model 3 gives the most flexibility, but she is concerned about the feasibility of implementing it. 
• Jacquie noted that the idea of the "Super item" is similar to a "Container" record. Which is the preferred scenario? Ann-Marie agreed this is a good question. 
• Jackie Gottlieb (via chat) - "Do we know how the Super-Item would be related to the instance?" - Laura acknowledged she is not sure that was discussed.
• Jessica - Development work would be needed in any case to make associations between items. To create bound-with relationships some change in FOLIO will be needed to make associations.
• Charlotte- Can the concept of the "Effective" location or call number be used here? Can we have an "effective" barcode for example.
• Conclusion: Slight preference for Model 2. Need more examples and use cases to hold up against Model 2 to make sure it will stand. Needs to be done in a timely manner. Do any of these models work for in-analytics? Please add to the document or send to Laura and she will put them in.

Result list Improvements:

UXPROD-1634 Inventory. Result list Refined display rules - establish small working group which to define short term improvements. 

UXPROD-1730 Inventory. Result list. Display elements should be configurable - long term solution.

Inventory UI Improvements:

Short term improvements using the MCL component (multi column list)

Long term improvements using a new component for Card display (loop in UX designer and the Stripes Force team)

Add more ideas here

https://docs.google.com/document/d/1u1tvfVxn6i3fTImrWWCYHlh7RT5cf3_G7YgDuxKob4M/edit