[OPEN-ILS-GENERAL] periodical claim in Evergreen Beta 3

[Mieke Stroo]

Hi Lebbeous,

Thanks for your information. 
Could you give some indication on when the developers will address the matter of connecting Acquisitions and Serials?

Mieke

-----Oorspronkelijk bericht-----
Van: open-ils-general-bounces at list.georgialibraries.org [mailto:open-ils-general-bounces at list.georgialibraries.org] Namens Lebbeous Fogle-Weekley
Verzonden: 02 December 2010 17:24
Aan: Evergreen Discussion Group
Onderwerp: Re: [OPEN-ILS-GENERAL] periodical claim in Evergreen Beta 3


On Thu, 2 Dec 2010 13:38:46 +0100, Mieke Stroo <mst at iisg.nl> wrote:
> Hi all,
> 
> A team at the IISG in Amsterdam is testing Evergreen Beta 3. When trying
to
> 'subscribe' to a periodical we came across a problem. This may be due to
a
> language problem, but we cannot figure out what exactly to fill out in:
> 
> 1. Claim types
> * code
> 2. Claim event type
> * code
> 3. Claim policy
> * claim policy name
> 4. Claim policy actions
> * action (event type)
> * claim policy ID
> 
> It is still impossible to print a claim and therefore impossible to check
> the consequences of what we fill out. Does anyone know the answer to
this?
> 

Claiming as it exists so far is part of Acquisitions, but not of Serials. 
Acquisitions and Serials in Evergreen do not yet interact.  The
Acquisitions subsystem is mainly working for monographs for now.  Designing
and implementing the way that Acquisitions and Serials will work together
is something the developers hope to address in the future.

> In connection to this:
> How to use "label" [in distributions] and "routing label" [in new
stream].
> So what to fill out here?
> 

A distribution's label will only appear in the receiving interface, and on
routing lists (if you use them; available in trunk only so far).  So it can
be pretty much anything.  If I'm subscribing to a magazine and there's a
distribution going to Branch One, I might just label it "Dist to BR1." 
It's a pretty minor field.

> Last question is, is it compulsory to fill out a "receive unit template"
> [in distributions] and how and where should one install this template?
> 

In the staff client, see Admin -> Local Administration -> Copy Template
Editor to create a copy template, which will be available for selection
when you return to the "Receive unit template" dropdown.  At minimum the
copy template will just need a name and an owning library.  If you want
barcoded items (so perhaps they can circulate or have holds placed on
them), be sure you have values set for "circulate," "holdable," and "opac
visible" set how you like.  You also need values for "fine level" and "loan
duration."  In trunk, you don't have to worry about "fine level" and "loan
duration," since there are drop-downs for those fields that default to
"Normal."  In beta3, there may still be simple textboxes, into which you
have to enter 1, 2 or 3, but I'm not sure off the top of my head if this is
still the case.  2 means normal.

> Sincerely,
> 
> Mieke Stroo
> IISG

Good luck!
-- 
Lebbeous