Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Christie Thomas presented the results of the Data Import Orders Survey Results. There were 9 responses from 4 institutions
Main pain points for those using Data Import for Orders include: ISBN validation, order creation with or without underlying SRS, record ordering for creation and matching to existing instances.
Obstacles for those not using Data Impot module to create orders include: editing and linking of Import profiles inefficient, unclear how to implement for a consortium, unrefined matching can result in duplicates and incorrect and uninformative logs.
Programming Data Import SIG can provide to encourage usage: testing, functionality, demonstrations and training and documentation.
Christie Thomas mentioned the changes in field mapping are not keeping up with functionality. How do we address this?
Ryan Taylor replied that development work going forward will try to keep the work in sync.
Next steps: Demonstrations-- How and when would people like to have demonstrations presented?
There was a general consensus that people want the information recorded.
Christie Thomas and Jennifer Eustis discuss how the Data Import SIG can work on creating documentation for MARC Orders. The documentation and demonstrations will initially be in the Data Import SIG documentation pages, but can be added to ‘Additional Topics’ on folio.org and eventually added to docs.folio.org
Concern about creating documentation is that processes change from version to version.
How does the FOLIO community envision the functionality MARC Orders?
Jennifer Eustis mentioned that having Ryan Taylor walk us through what MARC Order does and how would be helpful in understanding where the gaps are in functionality and help to create documentation.
Christie Thomas suggested putting out a poll on for dates and times for Data Import Lab, so that more people have an opportunity to attend.
Christie Thomas asked attends from the Acquisitions SIG, what could we do, so they can learn more about MARC Orders in Data Import and potentially be involved in the Data Import SIG?
Dung-Lan Chen responded that cross posting about topics, recording demonstrations and letting people know where the resources will live would be very helpful.
Upcoming meetings/agenda topics: --
Chat:
Molly Driscoll on MARC Orders in Data Import: A couple recent examples of Orders app functionality changing/developing, but not being reflected in the profiles:
LCCN is a supported product ID in Orders, but not in the DI field mapping profile. This removes a potential instance matching point when using this workflow.
Custom fields on orders/POLs do not yet appear in field mapping profiles.