ERM implementers
NEW ERM implementation topics, questions or issues
Please add questions and topics here. Topics or questions posted in slack will be added here as well.
Status
NEW Open topic that is not yet discussed with the SIG
App | Topic | Description/ use case | Date added | Provided by | Discussed in meeting: link | Actions / JIRA ticket | Status | |
---|---|---|---|---|---|---|---|---|
1 | Agreements | Numeration of Agreement lines | It would be helpful to have a number for Agreement lines to refer to Discussion on requirements and possible approaches (serial management pattern number via the number generator / POL approach) | Feb 7, 2024 | From ERM SIG discussion 2024-02-07 - ERM meeting |
|
| new |
2 | Licenses | Term field values resetting upon changing term types. | When working on a term, if you put content into either the internal or public notes, or set visibility from internal to public, then changing the term type will also reset all of those fields. It makes sense that the term’s value(s) field would reset, since those can be different for every term, but it’s harder to understand why this is the case for the other fields, and it seems like it could lead to lost work. | Sep 10, 2024 | @Clara Marino - Amherst College / Five Colleges |
|
| NEW |
3 | Dashboard | Filter for agreements that have no “Renewal priority” set | Description: a user wants to create a Dashboard widget that shows all agreements where the renewal priority is NOT ‘Cancel’. To do this, the user selects the ‘Renewal Priority’ filter and sets it to ‘is not definitely_cancel’ Current behaviour: All agreements are displayed that have a value for the renewal priority that is not ‘Cancel’. However, all agreements that have no value at all for renewal priority are left out. Wish:
| Sep 12, 2024 | @Martina Schildt on behalf of GBV library |
|
| NEW |
4 | Licenses | Adding tags for License Amendments | Our Licensing Librarian would like to track metadata for each document signed (e.g., signatory, fiscal year, type of purchase, etc.). He wants to record this information at both the license and the license amendment levels. Tags would be ideal for this purpose, but they are currently only available at the license level. Would it be possible to make tags available at the amendment level as well, similarly to how they are available at the Order and Order Line levels, the Agreement and Agreement Line levels? | September 21, 2024 | @Irina Trapido (Stanford) |
|
| NEW |
5 | Dashboard | Filter for agreements with no Description |
| Feb 4, 2025 | @Vidhya Ramachandran on behalf of Arkansas Colleges of Health Education |
|
| NEW |
OPEN ERM implementation topics, questions or issues
Status
in jira JIRA ticket created, work outstanding or in progress
Discussed Topic is discussed in SIG, needs JIRA ticket to be created
App | Topic | Description/ use case |
---|