2024-02-20 Acquisitions Meeting notes

Aaron Neslin

Kathleen Norton

Nina Stellmann

Alissa Hafele

Kimberly Pamplin

Okay Okonkwo

Ann Crowley

Kimberly Smith

Peter Sbrzesny

Björn Muschall

Kimberly Wiljanen

Rachel Sneed

Catherine Tuohy

Kristin Martin

Rhonda Fuhrmann

Corrie Hutchinson

Linh Chang

Sabrina Bayer

Dennis Bridges

Lisa Smith

Sarah Kees

Dung-Lan Chen

Martina Schildt

Scott Perry

Dwayne Swigert

Martina Tumulla

Steve Selleck

Heather McMillan

Masayo Uchiyama

Sven Thomsen

Jackie Magagnosc

Michael Phillips

Timothy Nelson

Joe Reimers

Molly Driscoll

Victoria Anderson

Julie Stauffer

Nancy Pelis

Winter White

Housekeeping

Dun-Lan

• Reminder - take a look at acq-sig-topics and vote whenever you get some free moments to help prioritize for development

  • agenda link - Agenda and Meeting Notes

    • Aaron Neslin 12:05 PM
      Looking at this link, I realized I didn't exclude closed and won't do issues.

• The fourth serials data alignment group meeting will take place this Friday at 9 am Eastern (Discovery would be the focus)

• Next meeting - Tuesday, Feb. 27, at 1 pm Eastern

:07

PC Update

PC Update (Kristin Martin ) -

• Overview of discovery survey: 2024-02-15

  • Sorting of data was a pain point mentioned

  • Serial and multi volume sorting in the discovery layer was the no.1 topic

• Review of evaluation process for new functionality: 2024-02-28

• SIG Updates: March

12

• The Leipzig team is adopting the custom fields in order.

• For Q release

  • Add custom fields in the POL

  • Be able to search and filter for custom fields

  • In the US, have custom fields in the template

•  

  Open

  

   

  Open

  

• Molly Driscoll 12:18 PM
  Are these fields able to be edited when the order is in an open or closed status? Or only in pending?

  • Can edit in Open orders as well as pending

• What does not work yet is searching for custom fields and filtering for custom fields.

• Pamplin, Kimberly B 12:20 PM
  Does the history track changes there?

  • It seems so, he checked while doing the demo. Dennis said some UI work may need to be done to display it.

• Kristin Martin 12:20 PM
  Are custom fields included in the export? Not yet
  Can a custom field be required? Yes

• Molly: Can the customable fields are mappable for libraries using mod gobi ?

  • no

• Kristin Martin 12:23 PM
  It would be great to have them included in the export. Especially since they can't be searched.

• Björn: Is there any need to change the current behavior from being able to edit custom fields in open orders?

  • no - leave it so the field can be edited in open status.

• Björn: 2nd question: Proposal would be to include custom fields text based custom fields in the keyword search.

  • Molly Driscoll 12:30 PM
    I like having them searchable via keyword and as dedicated options.

• Dennis: If the field is hidden, are they still searchable?

  • I believe so.

• Molly Driscoll 12:31 PM
  In Users, hidden fields are still searchable, but do not display.

• B Question: Some custom fields automatically shown as filter. They appear at the end of the list, not in alphabetical order with the whole list. Everyone was ok with this.

• In orders, custom fields are at the end of the view. Everyone was ok with this.

• Michael Phillips 12:36 PM
  Can you add a Created by filter to the Order lines search?

  • Dennis: This makes sense, but is probably independent of custom fields.

  • Dennis Bridges 12:38 PM
    I will add a story with the ace-sig-topics filter that includes adding “Create by” to the POL filters 🙂

    Michael Phillips 12:40 PM

• It is possible to delete custom fields. Deleting field will delete the data stored in the records. Is this ok?

• Michael Phillips 12:40 PM
  Would that deletion affect anything in the inventory? No, custom fields are stored in the orders.

  • Yes. A warning about which records would be impacted by a deletion.

• Martina: Initial reaction, don’t want to delete date. What about inactive or active custom fields., but prevent inactive ones from being used in new records.

  • Aaron: in agreements, you can mark one as deprecated in which case you can still search and view, but not added or edited.

    • Bjorn will take it to the team.

• Dennis: Even if you delete a custom field, the order history will still have the version history that includes that.

• Scott Perry (UChicago) 12:43 PM
  Couldn’t you also search first?

• Michael Phillips 12:45 PM
  Yes. But I still would like a warning about which records in which apps would be affected by a deletion.

  • Bjorn: It’s only about the Orders app.

• Molly Driscoll 12:46 PM
  It would also be wonderful to see the custom fields team adopt the enhancements you're making around search -- having the text field/text area types be searchable via their own search option, as well as via keyword search.

• Martina Schildt 12:51 PM
  I would like to keep the data 🙂 And just deprecated or inactive.

  • Several people agreed.

  • Bjorn: Can make it so we have both options. Ability to delete or deprecate.

• Dennis: If there is a multi select field, can you delete just one?

  • Yes.

• Kristin Martin 12:55 PM
  Will this be in Quesnalia?

  • Yes. Anything we talked about adding today may end up in the Poppy release.

• Michael Phillips: If you update ‘hidden’ to ‘suppressed’ in a custom field, will it update all the custom fields that have that term?

  • Bjorn: Will have to test that.

• Bjorn: Feel free to test in test environment and give him feedback.