Hi Olli,

There is a feature that may address some of your needs, and it's easy to miss, as it's new in 2.2 and only works in TPAC. It may be somewhat incompatible with academic library workflows, but Dan Wells could explain that better than I, and work can be done to make it better.

See here: http://www.esilibrary.com/esi/docs/?p=1245 , and skip to the bottom of the page for the screenshots to see whether you recognize it before reading the details in the text. If I've misunderstood you and you already know about this feature, disregard, but I suspect it isn't widely appreciated yet.

This, combined with copy paging in the TPAC, should prevent the page explosions that would otherwise be an issue with many holdings on a record.

That doesn't cover all the needs you're talking about, but I wanted to be sure you're aware of all the parts that already exist. I think this might be a usable foundation for you.

Hope this helps,

Lebbeous

On 08/17/2012 08:03 AM, Kivilahti Olli-Antti wrote:
Another feature specification:

We want to be able to show to our patrons what actual magazines we have 
available, checked-out, holdable, etc. Just like with normal holdings.
Currently we see the items, but they are not labelled, so there is no way to 
tell what volume or number this item represents.
Just adding the label to the mix won't cut it.
The current view will explode if we try to show a subscription with a lot of 
magazines. We can get 146 000 newspapers for the whole consortium (a radical 
stress case) in a 10 years time. If a patrons was to enter the detailed view 
for this newspaper, it would literally explode.
We are proposing to create a hierarchial tree-model display of volumes, issuances, 
org_units and finally the physical serials. To make things user friendly, a "5 most 
recent issuances" (n, actually) section is created for our patron's pleasure. This 
enables our patrons the view the most recent serials without descending to the AJAX 
jungle of volumes-tree.

There is one limitation however. We find it unnecessary for a record to have 
multiple subscriptions. Limiting the amount of subscriptions per record to one, 
is at this moment of planning an assumption.

I am hoping to get some feedback from the community if this is a good approach 
and if I am forgetting/misunderstanding/screwing up something.

Functionality will be fully created, documented and maintained by the Joensuu 
Regional Library.

As usual, the more "detailed" schematics can be found from our project 
management system.
http://193.65.112.189:8080/browse/EGDEV-75

--
Olli-Antti Kivilahti
Open Library 2013
Library of Joensuu



--
Lebbeous Fogle-Weekley
 | Software Developer
 | Equinox Software, Inc. / Your Library's Guide to Open Source
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  [email protected]
 | web:  http://www.esilibrary.com

Reply via email to