DigAcq
Home
Ordering
and Set Up
Access
Problem Solving (digprob)
Managing
Vera Records
Licensing
Cataloging
NERD
|
Package-Level
Records in Vera
Kinds
of Packages
The Ejournals
Team has identified the following types of package records:
- True
package: This package level record in VERA will show to the public
and provides an entry point for users to all the titles included within
that package. We would use one purchase order number to buy this package
and individual titles would be listed as comes on numbers to the main
PO number. Examples of a true package are Muse, JSTOR, Blackwell STM
and Elsevier (with some nuances).
- Pseudo
package: This is a package that includes groups of tiles that are
related to each other from an E point of view (similar access) but it
is purchased using more than one purchase order number. Society publications
are a sometimes good example: (American chemical Society, American Institute
of Physics, and Royal Society of Chemistry).
- Interface-based
or Template package: This is a group of titles whose common element
is an interface and uses an established template to make new records.
This group of titles is considered a "package" based on provider/aggregator
only and has nothing to do with purchasing methods. Each title would
have a separate purchase order. Examples of this are Ingenta, Metapress,
Highwire.
- Aggregators
Template: This type of package represents databases, provides one
entry point and is represented in acquisitions as one purchase order
number.
- Publisher
Name Package: This is a group of titles that are often dependent
on print subscriptions. They have a common publisher but are ordered
individually using separate POs. [They often have acquisition structures
and access methods in common.] Examples of this type of package would
be Cambridge University Press, World Scientific, De Gruyter, MIT Press.
Field
Values in Records:
What fields should be filled in for a Package-Level Record?
|
Vera
Field |
Value |
Who? |
|
Hide |
True
Packages: No
All
other packages: Yes; also, see [PERMANENT HIDE] note in title field
below. |
record
creator |
|
Package |
parent |
record
creator |
|
See
Ref |
check
box if this record is telling you to look at another record for full
information |
record
creator, or anyone |
|
Related
Records |
check
box if this record has other related records that point to it |
record
creator, or anyone |
|
ID
# |
automatically
assigned by Vera |
|
|
Title |
Name
of the package; if record is Hide=Yes, include the phrase [PERMANENT
HIDE] at the end of the field |
record
creator |
|
Interface |
Choose
from the drop down list. Leave blank for Publisher Name package where
there are multiple interfaces for the same publisher (e.g., MIT Press) |
record
creator |
|
Publisher |
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. |
record
creator |
|
Type |
Ejournal |
record
creator |
|
URLNative |
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 |
record
creator |
Remote Access OK |
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. |
record
creator |
Licensed |
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. |
record
creator |
License Type |
Choices are listed in the drop down menu. |
record
creator |
|
Licensed
notes |
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. |
anyone |
|
Tech
Phone |
. |
. |
|
Contact
Info |
include
as detailed information as you can |
record
creator, or anyone |
|
Order |
For
True Packages and Aggregators, the PO Number on which the package
is paid.
Not
applicable for other kinds of packages |
record
creator, or anyone |
|
Payment |
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) |
usually
Ellen or Kim, but could be anyone |
|
Maintainer |
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. |
record
creator, or anyone |
|
Product
Sponsor |
drop
down list of subject selectors who are "responsible" for
the package (will be assigned by Ellen) |
usually
Ellen |
|
Acquisitions
Details |
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. |
anyone |
|