Re: [OPEN-ILS-GENERAL] 2.9 Community Demo Server will be down next week

[Kathy Lussier]

Hi all,

The 2.9 MassLNC community demo server is available again. Instructions 
for accessing this server and the 2.10 server hosted by Equinox are 
available at http://wiki.evergreen-ils.org/doku.php?id=community_servers.


Many thanks to Martha Driscoll from NOBLE and to Thomas Berezansky from 
MVLC for their help in getting the server set up in its new location today!


Kathy

On 06/07/2016 09:09 AM, Kathy Lussier wrote:

Hi all,

Sending along a reminder that the MassLNC community demo server will 
be temporarily taken offline today at 9:30 a.m. Eastern.


I'll send an e-mail out later this week when it's back up again.

Kathy

On 06/03/2016 10:10 AM, Kathy Lussier wrote:

Hi all,

The MassLNC community demo server that is hosting a 2.9 instance of 
Evergreen will be taken down on Tuesday, June 7 as we get it ready to 
move to a new location. We plan to have it up and running again by 
the end of next week.


Thank you!
Kathy





--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] Evergreen translations by the numbers

[Terran McCanna]

+1 to Eva!

Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
tmcca...@georgialibraries.org


On Wed, Jun 8, 2016 at 1:13 PM, Jane Sandberg 
wrote:

> +1 to reasonable exceptions (and everything else on this thread).
>
> On Wed, Jun 8, 2016 at 10:10 AM, Rogan Hamby 
> wrote:
> > I would only throw in that I think #1 is largely a guideline.  I think
> the
> > coordinator should have the discretion to make reasonable exceptions as
> > circumstances present.
> >
> >
> >
> > On Wed, Jun 8, 2016 at 12:07 PM, Cerninakova Eva 
> wrote:
> >>
> >> Hi all,
> >>
> >> I tried to summarize the previous discussion about (not) including
> >> languages and translations  to Evergreen according to actual
> translations
> >> activity/support:
> >>
> >> 1) For the future releases the translation should be supported only when
> >> it meets at least one of the following criteria:
> >>
> >> - At least  70 % of translations are complete
> >> - Translations have been updated within the past 12 months and
> at
> >> least 50 % are complete
> >> - It is known there is someone actively working on the
> >> translations
> >> - There is a known living Evergreen catalog using the given
> >> language
> >> - The en-* variation of translations should have an exception
> from
> >> criteria above as they are a special case.
> >>
> >> 2)  Role of translations coordinator
> >>
> >> - He/she should communicate with translators  and provide
> >> information from Evergreen translators to developers and vice versa
> >> - If possible he/she should help translators with issues related
> >> to Evergreen translations in Launchpad etc.
> >>
> >> 3) As I have already noted before I can volunteer as  a translations
> >> coordinator  at present.
> >>
> >> 4) It will be necessary to fix the person I shall communicate with.
> Should
> >> this person be release manager? Or anyone else?
> >>
> >> 5) I am planning to contact translators to all languages and find out
> >> information about the situation of particular  translations (if it is
> >> supported, used  etc.).  I suppose I will use Launchpad for it. However
> it
> >> will be very helpful if you send me names (or contact also if
> possible)  of
> >> translators if  you have an information about them.
> >>
> >> 6) From the previous conversation I understood that the proposal to skip
> >> some unused languages concerns the future releases. It seems reasonable
> to
> >> me as Idon´t think I will be able gather all  information necessary for
> the
> >> decision whether  (not) to include particular language soon enough
> before
> >> 2.11 release (I am currently working on a project with quite close
> deadline
> >> so I have limited time available).
> >> However If there is a general consensus that we want to cut off the
> >> unsupported languages immediately, according to criteria mentioned above
> >> following languages should be definitely included to Evergreen at the
> >> moment:
> >>
> >> cs-CZ  -- Czech (98,77 % complete)
> >> hy-AM  -- Armenian (79.18% complete)
> >> fi-FI  -- Finnish (73.09% complete)
> >> en-CA  -- English (Canada) (70.73% complete + "en-*" variation )
> >> en-GB  -- English (UK) (66,89 % complete - active within past 12 months
> +
> >> "en-*" variation)
> >> pt-BR  -- Brazilian Portuguese (58.84% complete -  active within past 12
> >> months)
> >> fr-CA  -- French (52.84% complete - active within past 12 months)
> >> es-ES  -- Spanish (39.57% complete but there is known activity and
> number
> >> of translations continues to grow every day :-) )
> >>
> >> 7) As a person trying to watch the new strings to translate I would
> >> appreciate having information about new parts of Evergreen to translate
> >> actually added to Launchpad. Does anyone know if it is possible to make
> some
> >> setting in Launchpad to get information about newly added translation
> >> strings? May be there is such function  and I only  was not able to
> discover
> >> it. Or  (in case it is not)  would it be possible to send me a message
> when
> >> new translation strings are added?  -  I will share the information with
> >> other translators too. Thanks a lot.
> >>
> >> Eva
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> ---
> >> Mgr. Eva Cerniňáková
> >> cer...@jabok.cz
> >> Tel. +420 211 222 409
> >>
> >> Knihovna Jabok
> >> http:/knihovna.jabok.cuni.cz
> >> Tel.  +420 211 222 410
> >>
> >> Jabok - Vyšší odborná škola sociálně pedagogická a teologická
> >> Salmovská 8, 120 00 Praha 2
> >>
> >>
> >> 2016-06-03 20:01 GMT+02:00 Rogan Hamby :
> >>>
> >>> If you're volunteering I think you would be great for the role.  :)
> >>>
> >>>
> >>>
> >>> On Fri, Jun 3, 2016 at 1:57 PM, Cerninakova Eva 
> wrote:
> 
> 
> 
>  2016-06-03 15:18 GMT+02:00 Galen Charlton 

Re: [OPEN-ILS-GENERAL] Evergreen translations by the numbers

[Jane Sandberg]

+1 to reasonable exceptions (and everything else on this thread).

On Wed, Jun 8, 2016 at 10:10 AM, Rogan Hamby  wrote:
> I would only throw in that I think #1 is largely a guideline.  I think the
> coordinator should have the discretion to make reasonable exceptions as
> circumstances present.
>
>
>
> On Wed, Jun 8, 2016 at 12:07 PM, Cerninakova Eva  wrote:
>>
>> Hi all,
>>
>> I tried to summarize the previous discussion about (not) including
>> languages and translations  to Evergreen according to actual translations
>> activity/support:
>>
>> 1) For the future releases the translation should be supported only when
>> it meets at least one of the following criteria:
>>
>> - At least  70 % of translations are complete
>> - Translations have been updated within the past 12 months and at
>> least 50 % are complete
>> - It is known there is someone actively working on the
>> translations
>> - There is a known living Evergreen catalog using the given
>> language
>> - The en-* variation of translations should have an exception from
>> criteria above as they are a special case.
>>
>> 2)  Role of translations coordinator
>>
>> - He/she should communicate with translators  and provide
>> information from Evergreen translators to developers and vice versa
>> - If possible he/she should help translators with issues related
>> to Evergreen translations in Launchpad etc.
>>
>> 3) As I have already noted before I can volunteer as  a translations
>> coordinator  at present.
>>
>> 4) It will be necessary to fix the person I shall communicate with. Should
>> this person be release manager? Or anyone else?
>>
>> 5) I am planning to contact translators to all languages and find out
>> information about the situation of particular  translations (if it is
>> supported, used  etc.).  I suppose I will use Launchpad for it. However it
>> will be very helpful if you send me names (or contact also if possible)  of
>> translators if  you have an information about them.
>>
>> 6) From the previous conversation I understood that the proposal to skip
>> some unused languages concerns the future releases. It seems reasonable to
>> me as Idon´t think I will be able gather all  information necessary for the
>> decision whether  (not) to include particular language soon enough before
>> 2.11 release (I am currently working on a project with quite close deadline
>> so I have limited time available).
>> However If there is a general consensus that we want to cut off the
>> unsupported languages immediately, according to criteria mentioned above
>> following languages should be definitely included to Evergreen at the
>> moment:
>>
>> cs-CZ  -- Czech (98,77 % complete)
>> hy-AM  -- Armenian (79.18% complete)
>> fi-FI  -- Finnish (73.09% complete)
>> en-CA  -- English (Canada) (70.73% complete + "en-*" variation )
>> en-GB  -- English (UK) (66,89 % complete - active within past 12 months +
>> "en-*" variation)
>> pt-BR  -- Brazilian Portuguese (58.84% complete -  active within past 12
>> months)
>> fr-CA  -- French (52.84% complete - active within past 12 months)
>> es-ES  -- Spanish (39.57% complete but there is known activity and number
>> of translations continues to grow every day :-) )
>>
>> 7) As a person trying to watch the new strings to translate I would
>> appreciate having information about new parts of Evergreen to translate
>> actually added to Launchpad. Does anyone know if it is possible to make some
>> setting in Launchpad to get information about newly added translation
>> strings? May be there is such function  and I only  was not able to discover
>> it. Or  (in case it is not)  would it be possible to send me a message when
>> new translation strings are added?  -  I will share the information with
>> other translators too. Thanks a lot.
>>
>> Eva
>>
>>
>>
>>
>>
>>
>>
>> ---
>> Mgr. Eva Cerniňáková
>> cer...@jabok.cz
>> Tel. +420 211 222 409
>>
>> Knihovna Jabok
>> http:/knihovna.jabok.cuni.cz
>> Tel.  +420 211 222 410
>>
>> Jabok - Vyšší odborná škola sociálně pedagogická a teologická
>> Salmovská 8, 120 00 Praha 2
>>
>>
>> 2016-06-03 20:01 GMT+02:00 Rogan Hamby :
>>>
>>> If you're volunteering I think you would be great for the role.  :)
>>>
>>>
>>>
>>> On Fri, Jun 3, 2016 at 1:57 PM, Cerninakova Eva  wrote:



 2016-06-03 15:18 GMT+02:00 Galen Charlton :
>
> Hi,
>
> On Fri, Jun 3, 2016 at 8:59 AM, Cerninakova Eva 
> wrote:
>
> > I wonder what  would the "translation coordinator" exactly mean?
> > Would it just meen to keep an eye on translation statuses and
> > activity in
> > Launchpad and  communicate with translators on one side  and
> > Evergreen
> > developers on the other side good time before the Evergreen release?
>
> Yes. In addition, a translation coordinator might also 

Re: [OPEN-ILS-GENERAL] Evergreen translations by the numbers

[Rogan Hamby]

I would only throw in that I think #1 is largely a guideline.  I think the
coordinator should have the discretion to make reasonable exceptions as
circumstances present.



On Wed, Jun 8, 2016 at 12:07 PM, Cerninakova Eva  wrote:

> Hi all,
>
> I tried to summarize the previous discussion about (not) including
> languages and translations  to Evergreen according to actual translations
> activity/support:
>
> 1) For the future releases the translation should be supported only when
> it meets at least one of the following criteria:
>
> - At least  70 % of translations are complete
> - Translations have been updated within the past 12 months and at
> least 50 % are complete
> - It is known there is someone actively working on the translations
> - There is a known living Evergreen catalog using the given
> language
> - The en-* variation of translations should have an exception from
> criteria above as they are a special case.
>
> 2)  Role of translations coordinator
>
> - He/she should communicate with translators  and provide
> information from Evergreen translators to developers and vice versa
> - If possible he/she should help translators with issues related
> to Evergreen translations in Launchpad etc.
>
> 3) As I have already noted before I can volunteer as  a translations
> coordinator  at present.
>
> 4) It will be necessary to fix the person I shall communicate with. Should
> this person be release manager? Or anyone else?
>
> 5) I am planning to contact translators to all languages and find out
> information about the situation of particular  translations (if it is
> supported, used  etc.).  I suppose I will use Launchpad for it. However it
> will be very helpful if you send me names (or contact also if possible)  of
> translators if  you have an information about them.
>
> 6) From the previous conversation I understood that the proposal to skip
> some unused languages concerns the future releases. It seems reasonable to
> me as Idon´t think I will be able gather all  information necessary for the
> decision whether  (not) to include particular language soon enough before
> 2.11 release (I am currently working on a project with quite close deadline
> so I have limited time available).
> However If there is a general consensus that we want to cut off the
> unsupported languages immediately, according to criteria mentioned above
> following languages should be definitely included to Evergreen at the
> moment:
>
> cs-CZ  -- Czech (98,77 % complete)
> hy-AM  -- Armenian (79.18% complete)
> fi-FI  -- Finnish (73.09% complete)
> en-CA  -- English (Canada) (70.73% complete + "en-*" variation )
> en-GB  -- English (UK) (66,89 % complete - active within past 12 months +
> "en-*" variation)
> pt-BR  -- Brazilian Portuguese (58.84% complete -  active within past 12
> months)
> fr-CA  -- French (52.84% complete - active within past 12 months)
> es-ES  -- Spanish (39.57% complete but there is known activity and number
> of translations continues to grow every day :-) )
>
> 7) As a person trying to watch the new strings to translate I would
> appreciate having information about new parts of Evergreen to translate
> actually added to Launchpad. Does anyone know if it is possible to make
> some setting in Launchpad to get information about newly added translation
> strings? May be there is such function  and I only  was not able to
> discover it. Or  (in case it is not)  would it be possible to send me a
> message when new translation strings are added?  -  I will share the
> information with other translators too. Thanks a lot.
>
> Eva
>
>
>
>
>
>
>
> ---
> Mgr. Eva Cerniňáková
> cer...@jabok.cz
> Tel. +420 211 222 409
>
> Knihovna Jabok
> http:/knihovna.jabok.cuni.cz 
> Tel.  +420 211 222 410
>
> Jabok - Vyšší odborná škola sociálně pedagogická a teologická
> Salmovská 8, 120 00 Praha 2
>
>
> 2016-06-03 20:01 GMT+02:00 Rogan Hamby :
>
>> If you're volunteering I think you would be great for the role.  :)
>>
>>
>>
>> On Fri, Jun 3, 2016 at 1:57 PM, Cerninakova Eva  wrote:
>>
>>>
>>>
>>> 2016-06-03 15:18 GMT+02:00 Galen Charlton :
>>>
 Hi,

 On Fri, Jun 3, 2016 at 8:59 AM, Cerninakova Eva 
 wrote:

 > I wonder what  would the "translation coordinator" exactly mean?
 > Would it just meen to keep an eye on translation statuses and
 activity in
 > Launchpad and  communicate with translators on one side  and Evergreen
 > developers on the other side good time before the Evergreen release?

 Yes. In addition, a translation coordinator might also help
 translators if they have questions about how to use Launchpad and how
 to deal with any quirks of Evergreen's strings.

>>> O.K.
>>> I think I have already done some portion of translations in Lanchpad so
>>> it should not be a big problem 

Re: [OPEN-ILS-GENERAL] Evergreen translations by the numbers

[Ben Shum]

Re: 1:  I am +1 to the criteria, as they seem quite reasonable.

Re: 2, 3:  I say also +1 to translations coordinator role and yay,
thanks Eva for volunteering!

Re: 4:  I agree that the release manager can be a primary contact for
the translations coordinator.

Re: 6:  I think that initial list of languages seems a reasonable
starting point.  We can still add other languages back before the next
major series is released if they begin to show more activity per
criteria established.

Re: 7, that's a concern of mine in how development and translations
are being handled by the community.  Right now, the release process
steps list out that string freeze happens at "beta" time, meaning
prior to that point, any changes can be made to strings in master as
it develops.  Between beta and release, no one should merge any
changes that alter the strings in the files.

Launchpad does not appear to have any notification options for the
arrival of new strings to translate.  In the past, I think we used the
email announcement of "beta" to indicate that it was time to begin
translations by interested parties.  Given the timeframe though
between beta and release candidate / .0 first release, I have been
concerned that there is not enough time given over to translations.
When I was RM, I ended up unofficially making the .1 release an
additional translations sync to get more strings done into an actual
release.

Based on Mike Rylander's email regarding the 2.11 timetable (see
http://markmail.org/message/ygmnqu26lwuacnv6), I wonder if we should
consider doing multiple template string updates to try giving more
than just a chance at beta time.  Meaning, we should do a translation
templates (POT) sync at alpha time and beta time; with a freeze on
string changes at beta time.  And sync from Launchpad translations for
POs at beta, RC, and final release too to grab progress as it occurs.
That said, the vast majority of major changes happen at Beta time,
when most code changes get pushed in.

For devs, see:
http://wiki.evergreen-ils.org/doku.php?id=dev:release_process:evergreen:2.8#translations_i18n

Thinking ahead, the biggest changes will likely be for TPAC and
webstaff files with any catalog changes and new development for
modules in the web-based staff client.

-- Ben

On Wed, Jun 8, 2016 at 12:07 PM, Cerninakova Eva  wrote:
> Hi all,
>
> I tried to summarize the previous discussion about (not) including languages
> and translations  to Evergreen according to actual translations
> activity/support:
>
> 1) For the future releases the translation should be supported only when it
> meets at least one of the following criteria:
>
> - At least  70 % of translations are complete
> - Translations have been updated within the past 12 months and at
> least 50 % are complete
> - It is known there is someone actively working on the translations
> - There is a known living Evergreen catalog using the given language
> - The en-* variation of translations should have an exception from
> criteria above as they are a special case.
>
> 2)  Role of translations coordinator
>
> - He/she should communicate with translators  and provide
> information from Evergreen translators to developers and vice versa
> - If possible he/she should help translators with issues related to
> Evergreen translations in Launchpad etc.
>
> 3) As I have already noted before I can volunteer as  a translations
> coordinator  at present.
>
> 4) It will be necessary to fix the person I shall communicate with. Should
> this person be release manager? Or anyone else?
>
> 5) I am planning to contact translators to all languages and find out
> information about the situation of particular  translations (if it is
> supported, used  etc.).  I suppose I will use Launchpad for it. However it
> will be very helpful if you send me names (or contact also if possible)  of
> translators if  you have an information about them.
>
> 6) From the previous conversation I understood that the proposal to skip
> some unused languages concerns the future releases. It seems reasonable to
> me as Idon´t think I will be able gather all  information necessary for the
> decision whether  (not) to include particular language soon enough before
> 2.11 release (I am currently working on a project with quite close deadline
> so I have limited time available).
> However If there is a general consensus that we want to cut off the
> unsupported languages immediately, according to criteria mentioned above
> following languages should be definitely included to Evergreen at the
> moment:
>
> cs-CZ  -- Czech (98,77 % complete)
> hy-AM  -- Armenian (79.18% complete)
> fi-FI  -- Finnish (73.09% complete)
> en-CA  -- English (Canada) (70.73% complete + "en-*" variation )
> en-GB  -- English (UK) (66,89 % complete - active within past 12 months +
> "en-*" variation)
> pt-BR  -- Brazilian Portuguese (58.84% complete -  active within past 12
> 

Re: [OPEN-ILS-GENERAL] Evergreen translations by the numbers

[Cerninakova Eva]

Hi all,

I tried to summarize the previous discussion about (not) including
languages and translations  to Evergreen according to actual translations
activity/support:

1) For the future releases the translation should be supported only when it
meets at least one of the following criteria:

- At least  70 % of translations are complete
- Translations have been updated within the past 12 months and at
least 50 % are complete
- It is known there is someone actively working on the translations
- There is a known living Evergreen catalog using the given language
- The en-* variation of translations should have an exception from
criteria above as they are a special case.

2)  Role of translations coordinator

- He/she should communicate with translators  and provide
information from Evergreen translators to developers and vice versa
- If possible he/she should help translators with issues related to
Evergreen translations in Launchpad etc.

3) As I have already noted before I can volunteer as  a translations
coordinator  at present.

4) It will be necessary to fix the person I shall communicate with. Should
this person be release manager? Or anyone else?

5) I am planning to contact translators to all languages and find out
information about the situation of particular  translations (if it is
supported, used  etc.).  I suppose I will use Launchpad for it. However it
will be very helpful if you send me names (or contact also if possible)  of
translators if  you have an information about them.

6) From the previous conversation I understood that the proposal to skip
some unused languages concerns the future releases. It seems reasonable to
me as Idon´t think I will be able gather all  information necessary for the
decision whether  (not) to include particular language soon enough before
2.11 release (I am currently working on a project with quite close deadline
so I have limited time available).
However If there is a general consensus that we want to cut off the
unsupported languages immediately, according to criteria mentioned above
following languages should be definitely included to Evergreen at the
moment:

cs-CZ  -- Czech (98,77 % complete)
hy-AM  -- Armenian (79.18% complete)
fi-FI  -- Finnish (73.09% complete)
en-CA  -- English (Canada) (70.73% complete + "en-*" variation )
en-GB  -- English (UK) (66,89 % complete - active within past 12 months +
"en-*" variation)
pt-BR  -- Brazilian Portuguese (58.84% complete -  active within past 12
months)
fr-CA  -- French (52.84% complete - active within past 12 months)
es-ES  -- Spanish (39.57% complete but there is known activity and number
of translations continues to grow every day :-) )

7) As a person trying to watch the new strings to translate I would
appreciate having information about new parts of Evergreen to translate
actually added to Launchpad. Does anyone know if it is possible to make
some setting in Launchpad to get information about newly added translation
strings? May be there is such function  and I only  was not able to
discover it. Or  (in case it is not)  would it be possible to send me a
message when new translation strings are added?  -  I will share the
information with other translators too. Thanks a lot.

Eva







---
Mgr. Eva Cerniňáková
cer...@jabok.cz
Tel. +420 211 222 409

Knihovna Jabok
http:/knihovna.jabok.cuni.cz 
Tel.  +420 211 222 410

Jabok - Vyšší odborná škola sociálně pedagogická a teologická
Salmovská 8, 120 00 Praha 2


2016-06-03 20:01 GMT+02:00 Rogan Hamby :

> If you're volunteering I think you would be great for the role.  :)
>
>
>
> On Fri, Jun 3, 2016 at 1:57 PM, Cerninakova Eva  wrote:
>
>>
>>
>> 2016-06-03 15:18 GMT+02:00 Galen Charlton :
>>
>>> Hi,
>>>
>>> On Fri, Jun 3, 2016 at 8:59 AM, Cerninakova Eva  wrote:
>>>
>>> > I wonder what  would the "translation coordinator" exactly mean?
>>> > Would it just meen to keep an eye on translation statuses and activity
>>> in
>>> > Launchpad and  communicate with translators on one side  and Evergreen
>>> > developers on the other side good time before the Evergreen release?
>>>
>>> Yes. In addition, a translation coordinator might also help
>>> translators if they have questions about how to use Launchpad and how
>>> to deal with any quirks of Evergreen's strings.
>>>
>> O.K.
>> I think I have already done some portion of translations in Lanchpad so
>> it should not be a big problem ;-)
>> I might probably need help with some issues like where I can  find
>> information on dates of new Evergreen releases and related matters   etc.
>>
>>
>> Eva
>>
>
>
>
> --
> --
> Rogan R. Hamby, Data and Project Analyst
> Equinox - Open Your Library
> ro...@esilibrary.com
> 1-877-OPEN-ILS | www.esilibrary.com
>
>

Re: [OPEN-ILS-GENERAL] Repeated Override Entry

[Thomas Berezansky]

I believe some patron-oriented permissions will auto-override, but it won't 
remember secondary authentication to do so. So if you have the override 
permissions already some of the overrides should be able to be remembered for 
that session.

The person doing the checkouts not having permission would be more of an issue, 
but using "Operator Change" to switch to the higher permission person could 
alleviate the repeated password entries at least.

Thomas Berezansky
Assistant Network Administrator
Merrimack Valley Library Consortium
4 High ST, Suite 175
North Andover, MA 01845
Phone: 978-557-8161

-Original Message-
From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of 
scott.tho...@sparkpa.org
Sent: Wednesday, June 08, 2016 09:05
To: Evergreen Discussion Group 
Subject: [OPEN-ILS-GENERAL] Repeated Override Entry

Hi,

Sometimes our libraries have occasion to check out a large number of 
materials in succession to a patron who may have an issue. An example would be 
PATRON_EXCEEDS_FINES. In our system, if someone with low permissions is logged 
in, the override must be entered for each item which can be burdensome if there 
are a large number of items. If someone with higher permissions is logged in, 
Force This Action must be clicked off for each item. Can Evergreen 2.9 be 
configured so that, once the override is entered once, it is in effect for the 
rest of the checkouts? Or once Force This Action is clicked, it does not need 
to be repeated for the rest of the checkouts? Or would this require development?

Thank you,
Scott

 

 

Scott Thomas

Executive Director

PaILS / SPARK

(717) 873-9461

scott.tho...@sparkpa.org

  

 

Re: [OPEN-ILS-GENERAL] Selfcheck questions

[Terran McCanna]

Chauncey,

Bug Squashing Day last week produced a fix to problem #2 - we have it on
our server now and it's working, would love to have you test on yours.

https://bugs.launchpad.net/evergreen/+bug/1528647



Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
tmcca...@georgialibraries.org


On Thu, Jun 2, 2016 at 2:03 PM, Chauncey Montgomery 
wrote:

> As we have begun to implement selfcheck, I have hit some snags and could
> use a little direction.  I was hoping some of you with more experience
> could shed some light on the following items.
>
> 1.  We're trying to get selfcheck to ignore copy alert messages, etc., so
> patrons don't see "Unable to check out item [BARCODE]. Please see staff,"
> every time there is an issue.  We put the value "COPY_ALERT_MESSAGE" in the
> "selfcheck override events list" in the Library Settings Editor.  When a
> barcode is scanned, we no longer get the error; however, nothing happens.
> The check out doesn't complete. In researching the issue, I came across a
> thread on the listserv (http://markmail.org/message/5wjs5ffyjgykx46z).
> It appears to be the same issue, but I didn't see a resolution.
>
> 2.  How do you configure selfcheck to accept patron barcodes and not their
> login names?
>
> Thanks for any assistance.
>
> CM
> --
> Chauncey G. Montgomery, MLIS
> Director/Fiscal Officer | Community Library
> 44 Burrer Drive | Sunbury, OH 43074
> 740-965-3901 | http://community.lib.oh.us
>

[OPEN-ILS-GENERAL] Repeated Override Entry

[scott.tho...@sparkpa.org]

Hi,
Sometimes our libraries have occasion to check out a large number of 
materials in succession to a patron who may have an issue. An example would be 
PATRON_EXCEEDS_FINES. In our system, if someone with low permissions is logged 
in, the override must be entered for each item which can be burdensome if there 
are a large number of items. If someone with higher permissions is logged in, 
Force This Action must be clicked off for each item. Can Evergreen 2.9 be 
configured so that, once the override is entered once, it is in effect for the 
rest of the checkouts? Or once Force This Action is clicked, it does not need 
to be repeated for the rest of the checkouts? Or would this require development?

Thank you,
Scott


Scott Thomas
Executive Director
PaILS / SPARK
(717) 873-9461
scott.tho...@sparkpa.org
[Description: Description: Training | SPARK - Pennsylvania's Statewide Library 
System]