Skip to end of banner
Go to start of banner

2022-08-17 Data Import Subgroup meeting

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Recordings are posted Here (2022+) and Here (pre-2022)                   Slack channel for Q&A, discussion between meetings

Requirements details Here                                                                    Additional discussion topics in Subgroup parking lot


Attendees: Ann-Marie Breaux (Deactivated) Jennifer Eustis 

Morning Glory

Agenda topics:

  • Order field mapping profile questions
    • UIDATIMP-294 - Getting issue details... STATUS
    • Go over POL limit override, Create separate POs based on MARC value 
    • POL Subscription fields: included as part of one-time order in Orders app; include in field mapping?
    • Overall screen - any questions or concerns?
  • Lotus HF3 Hot fixes for Data Import: 
    • Completed and officially released
  • Morning Glory Bug fixes for Data Import: 
    • View complete list here
    • View unclosed bugs here (should be completed by the end of next week)
      • Some issues have different solutions for Lotus HF versus MG Bugfix versus Nolana, e.g. MODSOURCE-509 - Getting issue details... STATUS versus MODSOURCE-528 - Getting issue details... STATUS , or MODSOURMAN-841 - Getting issue details... STATUS versus MODSOURMAN-843 - Getting issue details... STATUS ; fixed Lotus first, now MG in progress
      • MODDICORE-275 - Getting issue details... STATUS : tested on Snapshot, and seems to be working properly; would be good to have someone else test it on Snapshot and confirm, before we release it to MG BF
      • MODINV-709 - Getting issue details... STATUS :
        • Separate profiles for 1) match by POL and update Inventory records and 2) match by VRN and update Inventory records work properly
        • Aiming to fix in Nolana; use separate profiles as a workaround for MG
  • Nolana planned Bug Fixes for Data Import:
  • Deleting import logs via API: (Carry-over from last meeting)
    • Available as of Morning Glory
    • There was a Slack question recently about being able to delete Import logs via API as of Morning Glory. We have added some documentation in the Data Import tips and tricks. Please see this page: 4-Data Import Logs, in the last section: Deleting Import Logs via API.
    • Questions:
      • The log data can be queried and compiled via the LDP; what happens with that when 1) the log is marked for deletion (via the UI or API) and then 2) completely deleted in the next 24-hour sweep?
      • Can the log info still be queried via API when it has been marked for deletion but not yet deleted?
      • Jenn: Cornell started playing with log info via API, but stopped until they go live on Lotus
      • NOTE: This has nothing to do with the instance "mark for deletion" discussion

Upcoming meetings:

  • 24 August 2022 (last meeting before WOLFcon)
    • Combined meeting with quickMARC Subgroup, to go over MARC Authority and MARC Bibliographic headings linking (only manually for now, not via DI)
  • 31 August 2022 (Cancelled due to WOLFcon)
  • No labels