Hi Jesse,

I think I was probably wrong :-(
I looked once more again at the template and it seems to me that the
definition of CSV output in our system probably could not be configured by
the template "Circ History CSV". I don´t see  anything like "Checkout Date"
or "Due Date"  in the template in trigger event definition.  However, I
definitely have the Checkout Date,   Due Date and  Date Returned column in
checkout history CSV output in my account. So probably  the definition for
the CSV output would be somewhere else. I wonder if it could have changed
in some of the Evergreen versions (we use Evergreen   2.12)?
Sorry for the confusion.

Eva








---
Mgr. Eva Cerniňáková
cer...@jabok.cz
Tel. +420 211 222 409 <+420%20211%20222%20409>

Knihovna Jabok
http:/knihovna.jabok.cz
Tel.  +420 211 222 410 <+420%20211%20222%20410>
Jabok - Vyšší odborná škola sociálně pedagogická a teologická
Salmovská 8, 120 00 Praha 2


2018-01-17 14:56 GMT+01:00 Cerninakova Eva <cer...@jabok.cz>:

> Hi Jesse,
>
> You can configure  template for  the checkout history CSV download in the
> staff client:
> Admin > Local Administration > Notification/Action Trigger
> The name of the trigger event definition for CSV output is "Circ History
> CSV"
>
> However, in our system the  CSV is the same  (by default) as what  patron
> can  view in web browser.
> The template for CSV output looks like this:
>
>
> Title,Author,Call Number,Barcode,Format
> [%-
> FOR circ IN target;
>     bibxml = helpers.unapi_bre(circ.target_copy.call_number.record,
> {flesh => '{mra}'});
>     title = "";
>     FOR part IN bibxml.findnodes('//*[@tag="245"]/*[@code="a" or
> @code="b"]');
>         title = title _ part.textContent;
>     END;
>     author = bibxml.findnodes('//*[@tag="100"]/*[@code="a"]').textContent;
>     item_type = bibxml.findnodes('//*[local-na
> me()="attributes"]/*[local-name()="field"][@name="item_type"
> ]').getAttribute('coded-value') %]
>
>     [%- helpers.csv_datum(title) -%],
>     [%- helpers.csv_datum(author) -%],
>     [%- helpers.csv_datum(circ.target_copy.call_number.label) -%],
>     [%- helpers.csv_datum(circ.target_copy.barcode) -%],
>     [%- helpers.csv_datum(item_type) %]
> [%- END -%]
>
>
>
>
>
> Hope this helps ;-)
>
> Eva
>
>
>
>
>
>
>
>
>
> ---
> Mgr. Eva Cerniňáková
> cer...@jabok.cz
> Tel. +420 211 222 409 <+420%20211%20222%20409>
>
> Knihovna Jabok
> http:/knihovna.jabok.cz
> Tel.  +420 211 222 410 <+420%20211%20222%20410>
> Jabok - Vyšší odborná škola sociálně pedagogická a teologická
> Salmovská 8, 120 00 Praha 2
>
>
> 2018-01-16 20:34 GMT+01:00 Jesse McCarty <jes...@burlingtonwa.gov>:
>
>> Hello everyone,
>>
>>
>>
>> Was curious if anyone had any insight into configuring the check-out
>> history download and what gets included in the download? For our
>> consortium, when a patron has check out history enabled and is viewing in
>> the browser, there are columns for checkout date, due date and returned
>> date. However, when you download the CSV none of these are present in the
>> download. Is there a way to configure Evergreen to include these in the
>> checkout history download?
>>
>> Thanks in advance.
>>
>>
>>
>> Jesse McCarty
>>
>> City of Burlington
>>
>> Information Systems Technician
>>
>
>

Reply via email to