Skip to end of banner
Go to start of banner

2021-12-7 Acquisitions Meeting notes

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 6 Next »

Date

Attendees

OrganizationTotalIndividuals


































































Agenda

Discussion items

TimeItemWhoNotes
2 minutes afterHousekeepingSusan Martin
  • Looking at schedule for the rest of December.
  • Next Tues,, Dec. 14 as last meeting until we return in January.
9 minutes afterDisplay a history of edits for the order recordDennis Bridges
  • Keep track of all changes being made (by users and those that are system-triggered)
  • Workflow from user's perspective
    • In actions menu access to see "change log"
    • Clicking would take you to a full screen view of changes
    • Come from PO, land in change log, looks like a standard search and filter layout
      • Ability to search by keyword, etc.
      • Details captured: field, updated, source, old value, new value, note
      • Notes could be recorded regarding changes made
      • If you select a search result, rather than getting a full screen view of details you would see the notes field
      • User must go into change long to enter note.
      • Could be changing a number of things / collection of fields. e.g. Product ID, Qualifier, Product ID type - may be updating some or all
        • A couple of different approaches:
          • Possible that we consider edits you are making as a version.
          • Might be easier to follow what is going on if these are grouped as versions. 
          • You might make your note on the version
          • Either you can select the version and see all changes in 3rd pane or take an approach with hierarchical lists (version is top line of the table in results list and could be expanded to see all of the changes that were made for that version).
          • Does this area need to be more of a quick reference? 
          • Sara: Quick browse is definitely necessary. In current system can browse changes as they occur. Somewhat vague but give an idea of who did what when. Like the idea of a note. Having that option when necessary for more detailed information seems cool. If I clicked on something and then saw specific information in a third pane that would be nice. 
          • In hierarchical search, if your search hits on something in the accordion it would display expanded. Maybe also a toggle to open.
          • Browsability of second version is much higher that where you only have third pane.
          • From Julie Brannon (she/her) to Everyone 12:24 PM
            To elaborate on Sara's comments - in Aleph the order log keeps track of defined categories of transactions such as a change to order status, order created, note added so we can filter by type of change made.  Not sure if that helps.

And the log includes actions that were taken by the system - it would be helpful to have an entry when the system makes changes to an order based on business logic.  For example, the order payment status changes or the order is closed due to activity on a related invoice.

          • Sara: Have a barcode search that will highlight that barcode. If that was possible
          • Dennis: If notes do not show on the order record anywhere, does it still serve a purpose? 
          • Sara: Would be there be a flag on the change log that there is a note?
          • Dennis: Yes, but if you haven't come to the change log would not know that there are notes.
          • Sara: Would be okay with that.
          • POL have notes functionality. Might be interesting to be able to link those notes to changes being made in the change log. More complex; only really worthwhile if it were important to see these notes when looking at a POL.
          • Sara: How easy is it to toggle between order and order log?
          • Dennis: It is in the action menu. Could also open them in separate windows.
          • Will rely on source field to indicate whether changes are made by a user or the system.
          • Types of changes - would need to group all of the order data into categories. (e.g. what are all the status fields?)
            • Using the accordion headers might be interesting.
            • These were cost edits, location edits, etc.
            • From Sara Colglazier (MHC/5C) to Everyone 12:32 PM
              +1 to accordion headers
            • Julie: Only will show changes to specific things. Know that if I were coming to find information would not want to have to look through every version or iteration. 
            • From Sara Colglazier (MHC/5C) to Everyone 12:32 PM
              and source would be so helpful, like App Invoices, vs. EBSCOnet, vs. user X
            • Dung-Lan: When you showed POL note, under dropdown has different types of notes you can make. Will change log be a type? 
              • Dennis: If it was going to be valuable then I think we would need to do something like that. Linking would probably involve a specific note type. It wouldn't be easy to do, but if it's valuable would probably look something like that. 





Action items

  • No labels