CORAL

When updating a vendor/representative's contact information, please make sure you update this in the  Organizations module!

All associated resources (tied by organization role: provider, vendor, platform, publisher, consortium, etc.) will automatically see inheirited contacts from those organizations.

If you ONLY add a contact to a resource, you will not  see it in the Organizations tab.  The flow on information is not a 2 way "push".  Organizations pushes contact information to the Resources module; however, the Resources module does not push new/updated information back to the Organizations module.

(example:. an appropriate situation would be Mark is our rep for all Thompson Reuters products however Micah is the specialized rep for just the WestLaw product.  Micah could be added as a contact to the Resource (Resources module) whereas Mark should be added under the Organization module to Thompson Reuters)

Please ask Kat (ER Librarian) if you have questions!

Date format within CORAL (workflow notes, product details, and license PDF files, etc.) should be YYYYMonDD.  ex 2015Apr08)

Year "YYYY" in numeric format, 4 digits (ex. 2013)

Month "Mon"  in alpha format, abbreviated to the 3 letter standard. (ex. Nov, May, Jan, etc.)

Day "DD" in numeric format, 2 digits (ex. 29, 13, 06)

Organizations must be set up in the Organization Module before their role can be specified within the Resource Module  "Product Details"

Organization Role options include: Consortium, Vendor, Provider, Platform, Publisher, Library.

You can add multiple roles (even of the same type) and Organization can be listed in more than one role ( see Amigos in example screenshot).

Licenses should be attached in the Licensing module first.

Once uploaded, go to the Resources module, find or add the desired resource.

Then under the "Acquisitions" tab, edit the License

Once you start typing, the license you attached in the License module should be auto-completed and you can select the appropriate.

By attaching this method, the Resource is easily referenced by the License which it is covered by.

see "CORAL- workflow routing" -- "Associating a license to a resource" for more details and screenshots

Resource module

Once a resource is added, you can edit the "Product details" from the 1st tab on the right navigation column ("Product" tab).

Alias/Alternate Name/Name Change EXAMPLE:

There are multiple options:  Abbreviation, Alternate Name, Name Change, Database, A-Z Name (LibGuides)

You can add as many as applicable.

For Workflow and Maintenance Notes: please put your initials AND date (date format should be YYYYMonDD.  ex 2015Apr08)

Name the resource "Example Title [CANCELED]" --- name of database/journal being canceled followed by "[CANCELED]

see "CORAL: workflow routines" --- "Closing a resource" for more details and screenshots

In the interest of what would most likely be searched, the term "CANCELED" was chosen (rather than "closed" or "ceased").

2015-April

Title List Notes and Fiscal Year Notes should be added under PRODUCT tab (not Acquisitions tab).

Title Lists Notes should be added for Journal Packages (just like we do for eBook sales/collections).

Title Lists should also be added as Attachments whenever possible.  (especially Excel Spreadsheets)

2015 April 08 - KLM, ZV, TO, MT.  Discussions regarding how packages are worked and documented within CORAL. 

Decision:  One generic Package record (serves as Parent) and subsequent years of renewals should be added as Child Resources (be sure to include Year at end of Resource Name).
example:  Child record: "Springer Journals Package Renewal 2015".  Parent record: "Springer Journal Package"