2021-01-21 Metadata Management Meeting notes

Date

please put an 'x' next to your name in the list below the "Discussion items" if you are attending. Thanks!

Recordings

Recordings of meetings can be found in the Metadata_Management_SIG > Recordings folder on Google Drive: https://drive.google.com/drive/folders/0B7G8S7WF6N20YUM4My1oRTIxSHM

Discussion items

Notetaker?
Christie Thomas
PC update

Update on the planned hotfix release for Honeysuckle. https://folio-org.atlassian.net/secure/Dashboard.jspa?selectPageId=11502

WolfCon - starting to gather notes about what people will want in the next wolfcon. Survey: https://forms.office.com/Pages/ResponsePage.aspx?id=yjb6UNN98USePxvzmjljpX5kdc6A165Ph_UGfjPi5CpURDhJWFFGRVYxVk84Szk3TVMzWDBPQTRRRS4u

Discussion of quality control and how many bugfix releases are required. - A new plan proposed to move more test cases earlier into the process. Also presented to the POs and the POs are concerned that they already have too much to do. Will work towards the new updated procedures for testing as best as the community can given constraints on person resources. 

New scratch environment available for the developers. - Comment that it would be great for the SIGs to have access to the scratch environment. (In addition to folio-test, folio-snapshot, folio-dataload. These are always being updated and the data does not persist. The scratch environment will provide a more stable data set for the developers. Concerns about scale in using the scratch environment for inventory / data import - maybe place limitations on how many records can be imported at a time. 

Licensing - typically have embraced the Apache license, but this may be a change with elastic search. Reaching out to elastic search community. 

Optimistic locking - confirming that nothing has changed in terms of the plan. Concerns have been raised about the prioritization of this. Gathering information about where collisions might have happened and letting users know that a collision has happened. 

Governance task force reaching out to OLE partners requesting commitments from partners. 

Paul - UC Boulder - have funding to hire two developers that they will be contributing to the project. 

Call for nominees for the community council. Council does not currently exist but will. 

Next Friday at 10:00 AM (Eastern) a Q&A regarding the new governance model. 

Topic: FOLIO Governance Model question and answer

Time: Jan 29, 2021 10:00 AM Eastern Time (US and Canada)

https://us02web.zoom.us/j/89002950320?pwd=NUdYRTVnZ01wT3NxbWREQ2xST1VYUT09

Meeting ID: 890 0295 0320

Passcode: folio-lsp

Find your local number: https://us02web.zoom.us/u/kbybQtjhI5

Sprint review

Recording on YouTube

Near the end includes a discussion of the back end work that has been done regarding elastic search. There are also slides from the sprint review. (Linked from the description of the recording.)

Other updates, announcements

Magda Z will join us next week to discuss elastic search.

Kalilah G. will join us next week to discuss QuickMarc. 

Tenant settings for item listCharlotte Whitt

UXPROD-2663

UI only updateCharlotte Whitt

Feed back on UIIN-372



Since it has been a while - revisit the decision to include the hrid in the top of the record. HRID has been added to the banner for each record under the title in light gray. Can copy the HRID from the body of the record but not from the banner. Also includes last updated.

Instances:

Publication has been moved to the title level.

There is no separator between the title and publication information in the title display, so it is not clear where the title ends and the publication information begins.

Ann-Marie commented that there is a style to have a space-dot-space between elements in displays. Suggestion from the SIG that this be added to the FOLIO style guide so that it becomes common practice and that the space-dot-space convention is not in conflict with punctuation practices within the data elements.  Charlotte will initiate this discussion regarding the style guide.  

Another issue - Do we need to spell out the instance record at the top of the page? It is for the machine reader. Even though it takes a lot of characters in the banner, it is a required element for accessibility. Maybe we can just have the instance icon and the record type, and not include "record". Question: is the label tied to the icon? If we change instance record to instance in one location and not others? Or will the change apply to all instances of the icon / label? A SIG member noted that the alt text will include the name for the icon and will be picked up by the screen reader. 

Items: 

Do we need input from resource access? Charlotte can reach out to Jana and ask them to take a look after she has style guide feedback. 

The barcode will be in the header in bold and the item hrid will be in the subheader in light grey. 

Suggestion that the headers be hot links to the instance or the holdings where information about these are included after the sub-header. 

Some institutions will use the hrid as the barcode when there is no barcode. Both will be displayed in this case. Members seem okay with this. 

Additional feature for feedback: modify item list in the top of the instance record. UXProd-2663. Looking into a solution that allows each user to modify the display according to what you are working on currently and this will be remembered for the current session for the user until a solution is available as a setting.

Question about what is a session? Ann-Marie thinks that it is when you close the window. Even if you are still logged in. Charlotte suggests that it is until you log out. It is not clear what a session is. SIG member points out that the session will end when you refresh the page. If a session is that short, then this is "a lot of clicking to hide columns". A couple of comments in chat that this is nice, but they would prefer that development be focused on more long-term development. Will these modifications get us further towards the long-term solution? Another comment in chat that this would be nice for exporting for reports. And another comment that this would be more important for some users than others - working with serials would be easier if the user can move the enumeration to a different spot. Comment that getting rid of columns at the tenant level when institutions do not use a property at all. 

Printing options across FOLIO

App Interaction Discussion Notes

Sept 18 2020

Sept 23 2020

Printing, for now, will be solved by exporting results: some mock-ups

UXPROD-2665 addresses Acquisitions

Acquisitions data in Holdings and Item records

See

UXPROD-1925 and UXPROD-1995

These features will not be completed in R1 – what are possible workarounds when loading order data?

Documentation/Training resources planningLaura E Danielsplaceholder

present?

Name

Organization


Aaron TrehubAuburn
XAnn-Marie BreauxEBSCO
XAnn KardosUMass Amherst

x

Charlotte WhittIndex Data
XChristie ThomasChicago
     XChristin Seegerthbz

Colin Van AlstineSmith (FC)

Damian Biagi

Dennis BridgesStacks
XDennis ChristmanDuke University
     Douglas ChorpitaGoethe Uni Frankfurt
XDracine HodgesDuke University
X

Felix Hemme

ZBW

Filip Jakobsen
XJacquie SamplesDuke University

Jason KovariCornell
XJenn ColtCornell
XJennifer EustisUMass Amherst
XJessica JaneckiDuke University
XJoshua BartonMichigan State

Kristen WilsonIndex Data
xLaura DanielsCornell

Lisa FurubottenTexas A&M
regretsLisa McCollLehigh University

Lisa SjögrenChalmers

Lynn Whittenberger

Magda ZacharskaEBSCO
XMartina Schildt

VZG


Molly DriscollEBSCO

Nancy Lorimer

Stanford

XNatascha OwensChicago

Niels Erik Nielsen
XPatty WanningerEBSCO
XRita Albrechthebis-Verbundzentrale
XSara ColglazierMHC/5C

Tiziana Possemato

Theodor Tolstoy

EBSCO


Wayne Schneider

Index Data


    regretsJesse LambertsonUniversity of Chicago
XRaegan WiechertMissouri States University