Assuming you intend for this to be done for the Template Toolkit OPAC, since this is for patron benefit, I would like to point out that an "AJAX jungle" would be highly undesirable. With very few exceptions I believe we are aiming for "no JavaScript needed to search, view information, place holds, etc".

Thus, each "new page" you wish to show would need to be an actual page load.

If you intend it for the JavaScript OPAC I would re-consider as the community is moving towards removing that OPAC entirely.

As for "assume there is only one subscription" - Unless the system enforces this already I would recommend *not* developing to that assumption. So long as the system supports it someone will do it.

Other than those two points I don't currently see any immediate other issues, but we don't currently use serials so I don't know a lot of the ins and outs.

Thomas Berezansky
Merrimack Valley Library Consortium


Quoting Kivilahti Olli-Antti <[email protected]>:

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



Reply via email to