Package-Level Records in Vera

True Packages: No

All other packages: Yes; also, see [PERMANENT HIDE] note in title field below.

Name of the package; if record is Hide=Yes, include the phrase [PERMANENT HIDE] at the end of the field

For Backfile packages, include the number of titles in this field; e.g., "Wiley Neuroscience Backfile (14 titles) [PERMANENT HIDE]"

Use the name of the publisher for True packages, Pseudo Packages, and Publisher Name Packages.

Do not use for Interface-based or Template packages, or for Aggregators Template.

True and Aggregator packages: the URL for the main page for the package

Interface-based or Template: the URL for the main page for the interface

Pseudo and Publisher Name: price list, or general web site address for publisher

Backfile Package: URL for the main page for the package, or the publisher's web site

Yes; remember that "licensed" here means that you had to work with the publisher / interface provider to set up access. Even if there is no license or terms at all, if you have to do something to set up the access, this field should say Yes.

Backfile Package: use whatever is in the main package level record

Choices are listed in the drop down menu.

Backfile Package: use whatever is in the main package level record

IP Address means the site authenticates MIT users based on their IP address. In this case, Licensed will say Yes.

Password means the site authenticates MIT users based on a username and password combinations. In this case, Licensed will say Yes.

None means the site doesn't authenticate MIT users at all, because the content is freely available to anyone. In this case, Licensed will say No.

Yes; we are assuming that Remote Access is allowed and setting this field to yes (for both the package level record and the title level records), UNLESS we see something in the terms that disallows this access.

Backfile Package: use whatever is in the main package level record

We are assuming that there are no access exclusions unless they are explictly stated in the license.

Newly created package level records: leave blank unless told otherwise.

Updating existing package level records: leave as is unless license is re-evaluated

We are assuming that there are no simultaneous user limits unless they are explicitly stated in the license.

Newly created package level records: leave blank unless told otherwise.

Updating existing package level records: leave as is unless license is re-evaluated

We are assuming that there are no restrictions on use unless they are explicitly stated in the license.

Newly created package level records: leave blank unless told otherwise.

Updating existing package level records: leave as is unless license is re-evaluated

For True Packages, Aggregators, and Backfiles, use the PO Number on which the package is paid.

Not applicable for other kinds of packages

how will the payment will be made

Split pay details are recorded here, and can also record to which party payments are made (e.g., print payments to Swets/OH, online payments to publisher, which is true for Wiley, Elsevier, Springer, and others I'm sure)

For Backfile Packages, include the total amount paid and the fiscal year; e.g., "$37,000 in FY2008"

what kind of "package" is this? Use the terms from the above list.

PRICING MODEL [year]
In order to keep track of the changing pricing models, using the standard phrase "PRICING MODEL 2006" (or whatever year you're talking about) and describe the pricing model (e.g., online free with print; print is 10% of list, online is 100% of list; print is 100% of list, online is an additional 5%; etc.)

Since this field can get long quickly, separate CURRENT INFORMATION from HISTORICAL INFORMATION. See ScienceDirect as an example.

Include detailed information about who to contact technical support / customer service; information about our Account Rep or other contacts may also be included.

Include phone numbers and email addresses; fax numbers and street addresses are generally not necessary.

Group vendors using the "Vendor ID: [CODE]" convention, and update all related records.

Update information in this field each time you do a PubCheck.

Any note information that has to do with the license.

See also more detailed instructions for Checking for License Terms.

ACTIVATION DETAILS
Include detailed instructions on how to activate titles, including URLs, login information, user names, passwords, helpful tips and tricks, etc. Ideally, this information would live it its own field, but for now it can go here. Be sure to include ACTIVATION DETAILS as a "header" before the information you type, and sign and date what you write.

LICENSE DETAILS
Include the URL of the terms, if they are passively mounted. Include any other pertinent licensing information here that can't be coded in other licensing fields. Be sure to include LICENSE DETAILS as a "header" for the information you type, and sign and date what you write.

MAINTENANCE DETAILS
Include detailed information about what it means to maintain this package. Be sure to include MAINTENANCE DETAILS as a "header" before the information you type, and sign and date what you write.

Backfile Package: Sally/Ellen may include LICENSE DETAILS; EJ Team should include CATALOGING NOTES to describe the progress of "cataloging" the individual titles for Barton, Vera, and SFX. No need to include ACTIVATION DETAILS or MAINTENANCE DETAILS on Backfile Package records.

drop down list of EJ Team members: tells who is the expert for this package

If the expert listed is "EJ-Team (any member of team)," it means that anyone on the EJ Team can handle the maintenance aspects of this package.