Message-Id: <s0ebede5.098@LAW.SYR.EDU> Date: Wed, 07 Jul 2004 12:34:36 -0400 From: "Andrea Rabbia" <arrabbia@law.syr.edu> Subject: [lawvoyage] Fwd: [VOYAGER-L]: Global Data Change Task Force Invitation
FYI, please respond directly to datatf@mailman.uwaterloo.ca
>>> Charles Woods <wcwoods@library.uwaterloo.ca> 7/7/2004 12:24:30 PM
>>>
The Global Data Change Task Force has been discussing various aspects
of global cataloguing data changes within Voyager for just over six
months now.
The foundations of a product due for release with Voyager 5.1 are
beginning to take shape.
We have been canvassing feedback from special interest and regional
interest groups, and have been pleased at the interest and enthusiasm,
shown in this product. It truly is needed!
We are concerned that we have a wide a spread of input, so that we do
not overlook particular needs. As a member of the wider Endeavor
community we are interested in your input to ensure that the product
that emerges really does address your needs for global-data-change
capabilities.
If you haven't already commented as part of a special interest or
regional group, would you please take the time to review a description
of the project below and comment on its direction and scope? Any and all
comments are appreciated.
Our address is:
(Please note that there have been some communication problems with a
previous mail alias -- if you have commented earlier to the datatf alias
and did not receive a response please resend your message to the address
above)
The Global Data Change product is defined as:
"An integrated solution for making mass data changes to bibliographic,
holdings, item, and authority records residing within the Voyager
database.
The purpose is to improve efficiencies and enable better work flows
using a safe and secure methodology."
Bibliographic, authority, holdings and item records are candidates for
global changes with this product.
* The product is being designed to work within the cataloguing module,
but able to take a file of record IDs selected elsewhere.
* GDC will provide a server-side function as well. This architecture
enables Voyager customers to program local solutions to interface with
this at a variety of levels
* Selection is being designed to include all normal cataloguing indexes
(including new MFHD searching), with the addition of fixed field and non
MARC data (such as date last changed, or PO attached for MFHDs), or
limiting against the database without a search e.g. to find single
characters etc.
* Changes may include tags, indicators, subfields and their content,
either string matched or individual, or in some cases a range of values
may be changed. Additions and deletions will also be incorporated.
* Record sets may be saved for change at a defined time.
* Issues of staff levels and security have been discussed, and a design
is being pursued that would allow some staff to define global changes
operations and other staff to run them. The need for a view only
capability is also recognised.
* Testing against a single open record will be supported, as well as
running a sample and producing reports, both pre and post global
changes.
* Definitions may be saved for re-use at a later time
* A methodology for automated management of jobs in the queue will also
be provided with GDC.
We are optimistic that this product will make the changes that we are
aware of within the client without the need for systems and programming
expertise.
Priorities:
However setting priorities is inevitable to enable GDC to achieve what
it does well, especially with this first release. Some indication of
your priorities for the product would be very helpful at this point of
time.
For example is it more important to enable more complex selection
options or a wider variety of transformations?
Is an intuitive user interface important or is the product to be used
mostly for specialised tasks that we expect just a few operators to
learn and use on a regular basis?
What are priorities for smaller Voyager libraries with fewer staff
doing a wider range of tasks?
Testing against real examples:
Although an imposition, in addition to comments on priorities, it would
also be very helpful to the team to receive further examples of
situations requiring global changes from you.
With each example if you could indicate which staff you consider should
be making this type of change, how often such a need arises or how big
the job is, it would be much appreciated.
Background information can be very valuable.
Real examples do not necessarily have to be used, just examples typical
of the type of change. Actual instances after the event can be difficult
to
track down. You could just resend earlier examples with the above
additional information.
We look forward to hearing from you by July 19.
Please reply to the Global Data Change Task Force:
datatf@mailman.uwaterloo.ca
(posted by Charles Woods on behalf of the Global Data Change Task
Force; special thanks to Patricia Scott of the University of Adelaide)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
VOYAGER-L : E-Mail List for the Voyager User's Group
Archives & Help Site: http://voyager.ship.edu/voyagerl
To Subscribe or Unsubscribe: Either use SupportWeb or
send a message to 'majordomo@voyager.ship.edu' and in the body of the
message include : 'subscribe voyager-l' or 'unsubscribe voyager-l'
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=