[OPEN-ILS-DEV] [OPEN-ILS-GENERAL] Planned Parts Development

[Hardy, Elaine]

Do you mean that the call number has the vols represented differently or
that your labels for monographic parts are different? I thought that how
the vol was designated in the call number didn't mater to the monographic
parts?

 

Elaine

  _____  


J. Elaine Hardy
PINES Bibliographic Projects & Metadata Manager
Georgia Public Library Service
1800 Century Place, Ste 150
Atlanta, Ga. 30345-4304

404.235-7128
404.235-7201, fax
ehardy at georgialibraries.org
www.georgialibraries.org
www.georgialibraries.org/pines




From: open-ils-dev-bounces at list.georgialibraries.org
[mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Tim
Spindler
Sent: Tuesday, January 29, 2013 2:37 PM
To: Evergreen Development Discussion List
Cc: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-DEV] [OPEN-ILS-GENERAL] Planned Parts Development

 

Elaine,

We have an issue from our migration where parts are represented in
multiple ways (v. 1, vol. 1, volume 1, v1, etc.).   With this development,
access to this would still be controlled by a permission so each
implementation would decide who has permissions to make changes on this.

Tim

On Tue, Jan 29, 2013 at 2:33 PM, Hardy, Elaine
<ehardy at georgialibraries.org> wrote:

Hope I'm wording this correctly. We haven't implemented Monographic parts
because of the need to retrospectively change volumes so I may not be
interpreting the functionality that exists correctly.

 

I have always thought that creating monograph parts should be done at the
consortia rather than the individual library level. In order for it to
work, all consortia members should use the same part label (retaining
their own volume designation within their call number). Have you
considering, rather than Pt 2 merging labels changing it to making
managing parts permissions at the consortium level rather than the local
level? That would solve the duplicate label issue and move the management
further up the hierarchical structure. This would essentially control the
part label vocabulary.

 

As a corollary, though not part of your request, to me creating call
number prefixes and suffixes should be at the library system level and not
at the consortium level. At least in PINES, call numbers are the
responsibility of the local library.

 

Elaine

  _____  


J. Elaine Hardy
PINES Bibliographic Projects & Metadata Manager
Georgia Public Library Service
1800 Century Place, Ste 150
Atlanta, Ga. 30345-4304

404.235-7128
404.235-7201, fax
ehardy at georgialibraries.org
www.georgialibraries.org
www.georgialibraries.org/pines



From: open-ils-general-bounces at list.georgialibraries.org
[mailto:open-ils-general-bounces at list.georgialibraries.org] On Behalf Of
Tim Spindler
Sent: Tuesday, January 29, 2013 11:38 AM
To: Evergreen Discussion Group; open-ils-dev at list.georgialibraries.org
Subject: [OPEN-ILS-GENERAL] Planned Parts Development

 

We are looking for comment on the proposed development.  Attached is the
specification.

-- 

____________________________

Tim Spindler

Manager of Library Applications

tspindler at cwmars.org

508-755-3323 x20 <tel:508-755-3323%20x20> 
IM: tjspindler (AOL, meebo, google wave)

 

C/W MARS, Inc.

67 Millbrook St, Suite 201

Worcester, MA 01606 
http://www.cwmars.org

 

P   Go Green - Save a tree! Please don't print this e-mail unless it's
really necessary.

 




-- 
Tim Spindler
tjspindler at gmail.com

 

P   Go Green - Save a tree! Please don't print this e-mail unless it's
really necessary.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20130129/36e51012/attachment-0001.htm>