Versions Compared

Old Version 17

changes.mady.by.user Lisa McColl

Saved on

compared with

New Version 18

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

Product Council UpdateFormer user (Deleted)

meeting notes: https://docs.google.com/document/d/1umiCI56ZL8CvA6uPuQ_Skz04la699js-sT0ArW6IxCE/edit

The Product Council was introduced to the new technical writer Marsha Borensztajn. Round 2 and Round 3 groups are being framed as MVP. Round 4 are implemented in Summer of 2021. These are "post-MVP" groups. Holly talked about ranking post-MVP features. The deadline for this will be June 1. New bilingual Product Owner, Lucy Liu, has begun and is working with the Shanghai Libraries.

Laura asked whether the group would like to meet to discuss MVP features together.

Subgroup & other updates?

Latest sprint review (slides) and video includes demos of data import, data export, resizable panes, normalized ISBN search, and filter by updated date

Data Import: good demo this week, and good feedback from the subgroup. Subgroup is working on protecting MARC fields during replace/overlay actions. Developers are working on lots of bug fixes from field mappings, plus the UI for MARC Modifications. We're also finishing the work to bring the Instance Preceding/Succeeding fields under control of the default MARC-Instance map. Once that happens, those Instance fields will not be editable any more if Source = MARC

Usability findings from Cornell: See link to report near bottom of this page


Bound-withs

How are these represented now? (demos from Raegan WiechertLisa McCollFelix Hemme Sharon Domier (5 Colleges) Natascha OwensLaura E Daniels)

How do we plan (or hope) to migrate this data into FOLIO?

What is the "ideal" model/behavior?

Review these two features:

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1856

  • Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-1044
  • Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-1045

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1241


  • Laura Wright - Cornell - Voyager - Laura demonstrated. 
    • Bibliographic record for the first title of a boundwith. That bib record has a holdings record.
    • 852 has a public note that includes a note, boundwith and provided slides.
    • There is one item per bound with. Public catalog (Blacklight) displays the titles that are part of the boundwith. The  Availability does not display accurately.
  • Reagan Wiechert - Sierra - Sierra does not use holdings - everything is in an item record. In Sierra, boundwiths are built by linking records together.  There is nothing explicit in the public catalog to expose this linking. Once you link records, there is no way to tell which one the item record was originally attached to. You can unlink records, although it is a cumbersome process. Reagan is not aware of a way to generate a list of boundwiths. 
  • Lehigh - OLE - https://confluence.cc.lehigh.edu/display/LTSTS/SC+TRX+-+Bound+withs
Feature ranking/gap analysis redux

for future meeting(s)

features:

https://docs.google.com/spreadsheets/d/1IoGBR4uWXCTDeag5tlMf0fRD0BFDb8r84IOgS0ZUUUE/edit?usp=sharing

ranking: https://docs.google.com/spreadsheets/d/1g8pCNmg2DrGJzUAtQHXPas8M9WIDXijnY4q666teeDc/edit#gid=0


Action: How can we effectively address features and prioritization? How can we look collectively at what has not yet been developed and what is most important?


Future MM meetings (ongoing)

Add ideas here

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


...