2021-12-10 Acquisitions Meeting notes

Meeting schedule for the rest of 2021 - Last meeting of 2021 will be Tuesday, December 14th.  We will resume our meetings on Tuesday, January 4, 2022. 

• Updates

  • PC Updates: SIG update from 2021-12-09 meeting.
    
  • New process for reviewing modules: PC review from a functional standpoint and then passes on to TC for review from technical side

  • Need new Product Owners for the following areas

    • • Loans, Check-in, Check-out, Loan information on Item Details (interim - Cheryl Malmborg)
      • Requests (interim - Brooks Travis)
      • Item State (interim - Charlotte Whitt)
      • Courses (interim - Charlotte Whitt)
  • Support SIG is looking for more members! Check with Anya.

Print Journal Routing Lists 

 #14 "Cover records" submitted by Sara Colglazier from the page. 

• Didn't discuss. No longer needed. 

#18 Print Journal Routing Lists 

• The Duke Law library uses functionality in Aleph to manage lists to route print journal subscription issues to faculty and staff.  Do other institutions do this and if so, would it be possible to add a JIRA so this could be considered for future development?  This isn't a high priority request, but it is functionality that exists in our current system. 
  1. Owen Stephens: I can’t imagine this is unique to Duke - I’ve worked in libraries where this has been a service
     
  2. Julie: Would like to print a list of names of faculty that want to see the print issue. Needs to be visible at the point of receipt, every time you receive something, that you can see the list of who needs to see it and print that routing list off. 
  3. From Lisa G Smith to Everyone 08:15 AM
     Our old system would print out names to route the issue to, followed by the location it should end up in.
     
  4. Dennis: Will need to start a wiki page for this. 
  5. Peter Sbrzesny: They can use that functionality as well. They also print out lists for issues that need to be circulated. 

Finance UI Enhancement Request: Select a fund, then select a budget for the fund. The Budget detail screen opens to a full window with the Budget name at the top. The Budget name is composed of the Fund code plus the fiscal year code (such as 'FY2022').  The Fund name isn't included on this screen and it would be very helpful to include it there, especially for libraries where the Fund code value isn't a close match to the Fund name  

It would especially help to have the Fund name viewable when using Actions such as Transfer or Allocate which are based on the Fund name.  As seen here, the Budget name displays at the top, but the Transfer action is based on Fund name - it would help to see the Fund name in the "Budget information" section as visual confirmation for the user when using the Transfer or Allocation actions.

From Scott Perry to Everyone 08:18 AM Codes are easier from my perspective.
From Lisa G Smith to Everyone 08:18 AM Mich State knows fund codes very well, too.
From Sara Colglazier (MHC/5C) to Everyone 08:18 AM +1 Julie about Codes rather than names
From Kristin Martin to Everyone 08:19 AM We love our codes too.

From Scott Perry to Everyone 08:20 AM I would love to make the name parenthetical with the code being first--perhaps user defined if codes are not universal.
From Ann Crowley to Everyone 08:21 AM To avoid the problem of missing codes, I added the code to our fund name

Dennis: Given the code is now there: is this a higher priority as well?
Julie: Adding the name would be a usability enhancement. 

From Dung-Lan Chen to Everyone 08:23 AM
+1 Julie!

no.21

The FTP details section of the Organization record contains credentials for the ftp server.  Could this group discuss the possibility of adding permission controls to display of the user name/password?  Currently, any user with permission to view the Organization record can view these fields.  To be consistent with the handling of credentials in the Interface section, it seems like this should be protected data through permissions. 

Dennis: We are going to start leveraging these details from the organization record, display these details full screen rather than on the recode. 

To have an export method, the current edi information displays on the record view. This shift means that we may have multiple integrations methods, So we are going to the a table of methods or integration detail. 

I imagine only certain people are editing these types of configurations. Is it important if we move these integration details to it's own screen, should there be a set of permissions associated with it?

• Sara: I don't see the need to make it complicated by locking it down.
• Julie Brannon: If it's in a separate screen where anyone who has view permission in the organization isn't seeing it, it just needs to be turned off for the general population. 
• Peter Sbrzesny: In our current system,  we only have the possibility to edit all data connected to a supplier. We have not had any problems, 
• From Lisa G Smith to Everyone 08:29 AM
  If one has permission to edit organizations, I think the permission should include the edi portion.

Updated mocks or  Display a history of edits for the order record

Discussion around canceling orders. Are their use cases for "unc-canceling: an order or order line?