Skip to end of banner
Go to start of banner

2023-02-22 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

Version 1 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) 

Current development (Orchid)

Agenda: 

    • Bugfest
      • DRAFT
      • Community prep meeting this Friday. If you want to participate, notify Ann-Marie or Oleksandr Bashtynskyi, to be added to teh Slack channel and get access to TestRail 
    • Creating orders from incoming MARC Bibs
      • Review current work on Folijet Rancher environment
      • Brainstorm for UAT
        • Field mapping profiles
        • Various job scenarios (pending, open, creating Inventory or not)
      • Aim for UAT  24 Feb-3 March

Upcoming meetings/agenda topics:

  • 1 March
    • Review of ISRI multiple profile UAT
    • How is Order import UAT going?
    • Review/confirm mockup for revised log for multiple holdings/items
  • 8 March
    • Continue log for multiple holdings/items (if necessary)
    • Review work from log subgroup and proposed updates in Poppy
  • 15 March
    • Discuss/review mockups for MARC updates refinements in Poppy
  • 22 March
    • Discuss Poppy scope


Chat:

Christie Thomas (she/her)  to  Everyone 1:12 PM
Fund code

Jennifer Eustis (she/her)  to  Everyone 1:12 PM
Fund Code

Jenn Colt  to  Everyone 1:12 PM
code
Right now default

Leeda Adkins  to  Everyone 1:16 PM
I think Duke plans not to use expense classes

Lynne Fors  to  Everyone 1:27 PM
Yes, keep the UI the same throughout

Dung-Lan Chen  to  Everyone 1:28 PM
Yes, makes sense to be consistent!

Christie Thomas (she/her)  to  Everyone 1:31 PM
That is definitely the case here at Chicago. We use the code.

Dung-Lan Chen  to  Everyone 1:32 PM
vendor code makes sense!

Jennifer Eustis (she/her)  to  Everyone 1:32 PM
Code would be better

Kimberly Wiljanen  to  Everyone 1:32 PM
Code

Dung-Lan Chen  to  Everyone 1:36 PM
not for us at the moment

Christie Thomas (she/her)  to  Everyone 1:37 PM
I don't think so. We have the account numbers coming from the vendor and we map if that is the case, but we ignore if not present.
+1 Jenn. Maybe we should have a UAT for this scenario to make sure that it does not matter?

Jennifer Eustis (she/her)  to  Everyone 1:42 PM
It's important for invoices - the accounting code linked to the account number

Dung-Lan Chen  to  Everyone 2:00 PM
Thanks, Ann Marie, I have to jump off for a reference shift!!

Jennifer Eustis (she/her)  to  Everyone 2:03 PM
I have to jump off for another meeting. Thanks Ann-Marie.

Jenn Colt  to  Everyone 2:03 PM
Looking at the default ISRI is very helpful if you  are going to make your own, especially if you need to update source folio and source Marc in different cases

Christie Thomas (she/her)  to  Everyone 2:04 PM
I have another meeting. See you next week.

Jenn Colt  to  Everyone 2:05 PM
Field protections!

  • No labels