| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-184 |
|---|
|
...
Requirement | Status | Use cases |
|---|
| Allow users to populate order bib data from material found in the KB | |
|
| Link POLs to Agreements/agreement lines AND instance records at the same time | | - Particularly with P/E mix material it would be helpful to be able to connect both areas of management from one place. So you are certain that people managing both workflows have the information they need to take over from acquisitions.
|
| When POL is linked to agreement/agreement lines allow users to leverage inventory interaction if desired. Creating instance, holdings, items if desired | | - Creating an agreement line for a package of electronic content that includes print. Currently the only way to identify that there is print material involved would be to link a POL that is PE mix. This POL would then point to somewhere that describes and manages the print component. This also users to track that both electronic and print material has been paid for. Also whether the print material has been received.
- User gets all titles electronically and there is a print copy included. Link to order to track that electronic has been paid for and that print material has been received.
|
|
| - Creating an agreement line for a package of electronic content references an order to facilitate the payment needed to acquire this resource. This allows the user to track whether the electronic material has been paid for.
- Acquisitions folks are generally responsible for where to acquire the material. The next step is to manage access to that material would be done by resource access people for print and electronic often stays with electronic resource management.
|
| Linking Agreement line to POL is NOT required | | - Material is provided by the consortia so library has agreements that aren't necessarily represented by orders in their system because they were acquired else where.
- Open access material is something that may be managed in ERM through an agreement but not necessarily have an order. Agreement would help manage access when nothing is acquired
|
|
| - Some of the decision making information about purchasing is done in the agreements order agreement lines. This information supports the purchasing decision.
|
Agreement lines can relate to multiple POLs.
| | - In the case of a mini bundle users may have multiple agreement lines that they want represented by one POL because they are acquired as one
|
| Package POLs can relate to multiple Agreement lines? | |
|
| | They have created an agreement for each of their eBook packages (e.g. EBSCO purchased eBooks, ProQuest purchased eBooks, etc.). Each agreement has a single agreement line, representing the package. However, they are linking multiple POL to the single agreement line to represent the orders for each of the titles. The 'Add PO line' button appears at the bottom of the attached POLs, so, each time they go to add a new POL, they need to scroll all the way to the bottom to click the button. This becomes quite arduous in instances where they have dozens (or more) POL attached to the agreement line. |
Proposed workflow:
Adding details to the POL
...
- Receiving title is linked to Title record in e-holdings
- If "Create inventory" set to Instance... then Receiving title also contains link to Instance if one could be found, if not then system creates one
- Are any special receiving workflows needed specific to "eholdings" title would piece be linked to these or to items?
Impact on "Receiving titles" for either Package or Title POL connected to eholding record
1) Titles may contain a link to the eholdings record AND the instance
Image Modified
Questions:
Question | Status | Conclusion | Comments |
|---|
| Where do we need to store references? Do we need them in both records? | | |
|
| Should we actually be building a mechanism that other applications can use to create orders | |
|
|
| |
|
|
...