[OPEN-ILS-DEV] Monograph Parts
Mike Rylander
mrylander at gmail.com
Wed Feb 16 12:56:14 EST 2011
On Wed, Feb 16, 2011 at 9:28 AM, Hardy, Elaine
<ehardy at georgialibraries.org> wrote:
> Mike,
>
> This is a great idea, particularly the holds prompt. Could you go into a
> little more detail on how this would function on the user side, both
> patron and cataloging staff?
For patrons placing a hold on a record where there are Parts in use,
they will see at least two new UI components
* On the record detail screen, there will be a list of Parts in use
on the record, with hold links next to them.
* Next to each copy, if it is attached to a Part, the Part label
will be displayed and will have a "Place a Hold" link next to it for
the part itself. Any copy on that record that is attached to the same
Part will be able to fill that hold.
* On the hold placement/edit screen, the user will see a list or
dropdown of in-use parts from which they can choose, and if they
choose one part (instead of the default "any") then they will be
placing a Part-type hold just as if they'd used one of the links
described above.
For staff, they will have an "Actions for this Record" interface for
maintaining (adding, removing, editing) the Parts available for use on
copies, and in the copy editor, the ability to attach a Part to a
copy.
> I'm particularly interested in how this would
> function in a consortium like PINES where different libraries might
> process a multipart set differently. For example, one library might
> process and circulate a 3 part DVD set as one item, where another might
> put each in a separate container with a separate barcode. How would it
> display in holdings maintenance as well as in the OPAC copy display?
>
In Holdings Maintenance, Monograph Part will need to be a new column
which will display the label from the Part. In the OPAC, in-use Parts
(scoped by the search to where you're searching, of course) will be
displayed to the user for hold placement and drill-down to call number
and copy information. They will also show up next to the copies
themselves in the traditional copy summary at the bottom.
All of that, of course, is skin-specific, and the display can be customized.
> Also, would this mean multipart items already held by a library would need
> to be change in Evergreen to take advantage of the functionality? Or would
> there be a way to automatically process multipart items retrospectively?
>
I will be working on some tools (though, after this is completed) to
identify common Part strings and, once identified, help libraries
retrospectively convert the trailing strings in call numbers to Parts.
It won't be automatic, but I believe we can automate the broad,
common cases like "v.{number}" and friends, or "{year}-{MONTH}".
--miker
> Elaine
>
>
> J. Elaine Hardy
> PINES Bibliographic Projects and Metadata Manager
> Georgia Public Library Service,
> A Unit of the University System of Georgia
> 1800 Century Place, Suite 150
> Atlanta, Ga. 30345-4304
> 404.235-7128
> 404.235-7201, fax
>
> ehardy at georgialibraries.org
> www.georgialibraries.org
> http://www.georgialibraries.org/pines/
>
>
> -----Original Message-----
> From: open-ils-dev-bounces at list.georgialibraries.org
> [mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Mike
> Rylander
> Sent: Tuesday, February 15, 2011 3:09 PM
> To: Evergreen Development Discussion List
> Subject: [OPEN-ILS-DEV] Monograph Parts
>
> I'll be starting work on an implementation of Monograph Parts (think:
> DIsks 1-3; Volume A-D; etc), well, right now, in a git branch that I'll
> push to http://git.esilibrary.com/?p=evergreen-equinox.git;a=summary
> but I wanted to get the basic plan out there for comment. So, attached
> you'll find a PDF outlining the plan. Comments and feedback are welcome,
> but time for significant changes is slim.
>
> This is not intended to cover every single possible use of the concept of
> Monograph Parts, but I believe it is a straight-forward design that offers
> a very good code-to-feature ratio and should be readily used by existing
> sites after upgrading to a version containing the code.
>
> --
> Mike Rylander
> | VP, Research and Design
> | Equinox Software, Inc. / The Evergreen Experts
> | phone: 1-877-OPEN-ILS (673-6457)
> | email: miker at esilibrary.com
> | web: http://www.esilibrary.com
>
--
Mike Rylander
| VP, Research and Design
| Equinox Software, Inc. / The Evergreen Experts
| phone: 1-877-OPEN-ILS (673-6457)
| email: miker at esilibrary.com
| web: http://www.esilibrary.com
More information about the Open-ils-dev
mailing list