Re: [OPEN-ILS-GENERAL] 3.2 Release schedule extension (was: feature freeze and more)

[Dan Wells]

Bill, I think this sounds fine, but would make two possible suggestions.

1) I think we should get some kind of release built before bug-squashing week, 
to be usable for anyone wanting that sort of testing path during the following 
week.  That could easily happen late on the 7th, or we could XUL/Angular merge 
on the 6th and have the 7th to build.  Whether this is branded as an alpha or a 
beta1 doesn't matter too much, though if it is "feature complete", beta1 seems 
more correct.

2) It is reasonable to expect this might lead to a need for a beta2, but my 
preference would be to make that call a little later on, as needed.  It is easy 
to add more delays, but assuming we'll need them all now means we'll never get 
the time back :)

Just my two cents.

Dan


From: Open-ils-general  on 
behalf of Bill Erickson 
Sent: Tuesday, August 28, 2018 6:11:01 PM
To: Public Open-ILS tech discussion
Cc: open-ils-general@list.georgialibraries.org
Subject: [OPEN-ILS-GENERAL] 3.2 Release schedule extension (was: feature
freeze and more)

Breaking this message out specifically to discuss extending the 3.2 release 
schedule.

We have a lot of competing priorities at the moment.  This week really should 
be about wrapping up feature merges, but the pending Beta is forcing us to 
address a number of outstanding issues, and each depends on the other.

Extending the release schedule seems perfectly reasonable to me.  My only 
concern is determining how best to leverage the Sept 10-14 bug squashing week.  
Ideally, all major changes would be merged so we can work out the kinks during 
the group bug squashing.

That means features, XUL removal, and Angular merging would need to be done by 
the end of next week, with time to spare to ensure all this chaos leaves us 
with a usable code base for testers.

To buy us some breathing room in the short term, I'll make this proposal:

Feature freeze pushed to Sept 4th.
XUL and Angular merge freeze Sept 7th.
Bug Squashing Sept 10-14
Beta Sept 19th (remaining targets pushed back 2 weeks as well).

This may not be the extension you were hoping for Kathy, and we can certainly 
modify this, but this at least gives us a little time to focus specifically on 
wrapping up the big ticket items before bug squashing ensues.

Suitable compromise for now?  Thoughts?

Thanks,

-b




On Tue, Aug 28, 2018 at 2:39 PM Kathy Lussier 
mailto:kluss...@masslnc.org>> wrote:
Hi Bill,

In looking at the list of showstoppers, I see one has a pullrequest, so it 
seems reasonable it could be tested and merged soon. For the other bugs, does 
anyone have a sense of whether any are particularly complex? Or are they mostly 
straightforward bugs that just haven't been addressed yet due to lack of tuits? 
If it's the latter, could we consider delaying the full release (with xul 
removal) until the showstoppers are fixed?

I'm concerned about the breakage that is likely to occur the longer we continue 
to make the xul client available in our releases, but these bugs were 
identified as real issues in getting libraries to adopt the web client. At this 
time, there are just a handful of remaining showstoppers, and if we can commit 
to getting them resolved before the full release, I think it will make a 
smoother transition to 3.2 for our libraries.

Kathy

--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org


On Mon, Aug 27, 2018 at 6:47 PM Bill Erickson 
mailto:beric...@gmail.com>> wrote:
Hi Scott,

On Mon, Aug 27, 2018 at 5:24 PM 
scott.tho...@sparkpa.org 
mailto:scott.tho...@sparkpa.org>> wrote:
Hi Bill,
I have two questions about this:


1.   You mentioned a vote. Who is the “we” that votes?

Good question.  This would be a core developer vote.   I started typing this as 
a developer list message, then added the general list just before sending...

>From my perspective, this vote is more about getting a public record of 
>developer buy-in (or otherwise) as is typically the case before proceeding 
>with a large architectural change.  It also acts as a "should we do this?" 
>safety valve.  However, I call the vote now because in my opinion as RM we are 
>ready to proceed and I suspect that's what we'll decide.  It's not done 'til 
>it's done, though.

It's also worth reminding everyone we are also providing extended support for 
Evergreen 3.1, so users can continue using the XUL client for a longer period 
of time.  Normally, a release is supported for 12 months of bug fixes, plus 3 
months of security fixes.  3.1 will be supported for a longer period of time -- 
duration TBD -- so sites will have more time before needing to upgrade to 3.2.  
This will buy us more time in the community to continue squashing bugs as well.

2.   If it is determined that not enough blockers are fixed, does this mean 
that a 3.2 version of XUL will be made 

Re: [OPEN-ILS-GENERAL] 3.2 Release schedule extension (was: feature freeze and more)

[Bill Erickson]

It occurs to me the XUL removal patch will not be as architecturally
significant as I had been thinking.  We will not (yet) be deleting the
entire directory tree, so the impact should be minimal for rest of the
Evergreen code.  Given that, extending the deadline for XUL removal a bit
further makes sense.

Updated proposal:

Feature freeze Sept 4th.
Angular merge by Sept 6th.
Bug Squashing Sept 10-14
XUL vote (and subsequent removal if approved) Sept 17th.
Beta Sept 19th (remaining targets pushed back 2 weeks as well).

Perhaps we can squash some of these blockers during the bug squashing week.

Comments welcome.

-b

On Tue, Aug 28, 2018 at 6:11 PM Bill Erickson  wrote:

> Breaking this message out specifically to discuss extending the 3.2
> release schedule.
>
> We have a lot of competing priorities at the moment.  This week really
> should be about wrapping up feature merges, but the pending Beta is forcing
> us to address a number of outstanding issues, and each depends on the other.
>
> Extending the release schedule seems perfectly reasonable to me.  My only
> concern is determining how best to leverage the Sept 10-14 bug squashing
> week.  Ideally, all major changes would be merged so we can work out the
> kinks during the group bug squashing.
>
> That means features, XUL removal, and Angular merging would need to be
> done by the end of next week, with time to spare to ensure all this chaos
> leaves us with a usable code base for testers.
>
> To buy us some breathing room in the short term, I'll make this proposal:
>
> Feature freeze pushed to Sept 4th.
> XUL and Angular merge freeze Sept 7th.
> Bug Squashing Sept 10-14
> Beta Sept 19th (remaining targets pushed back 2 weeks as well).
>
> This may not be the extension you were hoping for Kathy, and we can
> certainly modify this, but this at least gives us a little time to focus
> specifically on wrapping up the big ticket items before bug squashing
> ensues.
>
> Suitable compromise for now?  Thoughts?
>
> Thanks,
>
> -b
>
>
>
>
> On Tue, Aug 28, 2018 at 2:39 PM Kathy Lussier 
> wrote:
>
>> Hi Bill,
>>
>> In looking at the list of showstoppers, I see one has a pullrequest, so
>> it seems reasonable it could be tested and merged soon. For the other bugs,
>> does anyone have a sense of whether any are particularly complex? Or are
>> they mostly straightforward bugs that just haven't been addressed yet due
>> to lack of tuits? If it's the latter, could we consider delaying the full
>> release (with xul removal) until the showstoppers are fixed?
>>
>> I'm concerned about the breakage that is likely to occur the longer we
>> continue to make the xul client available in our releases, but these bugs
>> were identified as real issues in getting libraries to adopt the web
>> client. At this time, there are just a handful of remaining showstoppers,
>> and if we can commit to getting them resolved before the full release, I
>> think it will make a smoother transition to 3.2 for our libraries.
>>
>> Kathy
>>
>> --
>> Kathy Lussier
>> Project Coordinator
>> Massachusetts Library Network Cooperative
>> (508) 343-0128kluss...@masslnc.org
>>
>>
>>
>> On Mon, Aug 27, 2018 at 6:47 PM Bill Erickson  wrote:
>>
>>> Hi Scott,
>>>
>>> On Mon, Aug 27, 2018 at 5:24 PM scott.tho...@sparkpa.org <
>>> scott.tho...@sparkpa.org> wrote:
>>>
 Hi Bill,

 I have two questions about this:



 1.   You mentioned a vote. Who is the “we” that votes?

>>> Good question.  This would be a core developer vote.   I started typing
>>> this as a developer list message, then added the general list just before
>>> sending...
>>>
>>> From my perspective, this vote is more about getting a public record of
>>> developer buy-in (or otherwise) as is typically the case before proceeding
>>> with a large architectural change.  It also acts as a "should we do this?"
>>> safety valve.  However, I call the vote now because in my opinion as RM we
>>> are ready to proceed and I suspect that's what we'll decide.  It's not done
>>> 'til it's done, though.
>>>
>>> It's also worth reminding everyone we are also providing extended
>>> support for Evergreen 3.1, so users can continue using the XUL client for a
>>> longer period of time.  Normally, a release is supported for 12 months of
>>> bug fixes, plus 3 months of security fixes.  3.1 will be supported for a
>>> longer period of time -- duration TBD -- so sites will have more time
>>> before needing to upgrade to 3.2.  This will buy us more time in the
>>> community to continue squashing bugs as well.
>>>
 2.   If it is determined that not enough blockers are fixed, does
 this mean that a 3.2 version of XUL will be made available and XUL will not
 be removed until 3.3

 Yes, if the core developers vote not to proceed with XUL removal, it
>>> would be delayed until the next release cycle (3.3).
>>>
>>> Just to offer some perspective, from the dev side it's not just a
>>> question of how many web 

[OPEN-ILS-GENERAL] 3.2 Release schedule extension (was: feature freeze and more)

[Bill Erickson]

Breaking this message out specifically to discuss extending the 3.2 release
schedule.

We have a lot of competing priorities at the moment.  This week really
should be about wrapping up feature merges, but the pending Beta is forcing
us to address a number of outstanding issues, and each depends on the other.

Extending the release schedule seems perfectly reasonable to me.  My only
concern is determining how best to leverage the Sept 10-14 bug squashing
week.  Ideally, all major changes would be merged so we can work out the
kinks during the group bug squashing.

That means features, XUL removal, and Angular merging would need to be done
by the end of next week, with time to spare to ensure all this chaos leaves
us with a usable code base for testers.

To buy us some breathing room in the short term, I'll make this proposal:

Feature freeze pushed to Sept 4th.
XUL and Angular merge freeze Sept 7th.
Bug Squashing Sept 10-14
Beta Sept 19th (remaining targets pushed back 2 weeks as well).

This may not be the extension you were hoping for Kathy, and we can
certainly modify this, but this at least gives us a little time to focus
specifically on wrapping up the big ticket items before bug squashing
ensues.

Suitable compromise for now?  Thoughts?

Thanks,

-b




On Tue, Aug 28, 2018 at 2:39 PM Kathy Lussier  wrote:

> Hi Bill,
>
> In looking at the list of showstoppers, I see one has a pullrequest, so it
> seems reasonable it could be tested and merged soon. For the other bugs,
> does anyone have a sense of whether any are particularly complex? Or are
> they mostly straightforward bugs that just haven't been addressed yet due
> to lack of tuits? If it's the latter, could we consider delaying the full
> release (with xul removal) until the showstoppers are fixed?
>
> I'm concerned about the breakage that is likely to occur the longer we
> continue to make the xul client available in our releases, but these bugs
> were identified as real issues in getting libraries to adopt the web
> client. At this time, there are just a handful of remaining showstoppers,
> and if we can commit to getting them resolved before the full release, I
> think it will make a smoother transition to 3.2 for our libraries.
>
> Kathy
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 343-0128kluss...@masslnc.org
>
>
>
> On Mon, Aug 27, 2018 at 6:47 PM Bill Erickson  wrote:
>
>> Hi Scott,
>>
>> On Mon, Aug 27, 2018 at 5:24 PM scott.tho...@sparkpa.org <
>> scott.tho...@sparkpa.org> wrote:
>>
>>> Hi Bill,
>>>
>>> I have two questions about this:
>>>
>>>
>>>
>>> 1.   You mentioned a vote. Who is the “we” that votes?
>>>
>> Good question.  This would be a core developer vote.   I started typing
>> this as a developer list message, then added the general list just before
>> sending...
>>
>> From my perspective, this vote is more about getting a public record of
>> developer buy-in (or otherwise) as is typically the case before proceeding
>> with a large architectural change.  It also acts as a "should we do this?"
>> safety valve.  However, I call the vote now because in my opinion as RM we
>> are ready to proceed and I suspect that's what we'll decide.  It's not done
>> 'til it's done, though.
>>
>> It's also worth reminding everyone we are also providing extended support
>> for Evergreen 3.1, so users can continue using the XUL client for a longer
>> period of time.  Normally, a release is supported for 12 months of bug
>> fixes, plus 3 months of security fixes.  3.1 will be supported for a longer
>> period of time -- duration TBD -- so sites will have more time before
>> needing to upgrade to 3.2.  This will buy us more time in the community to
>> continue squashing bugs as well.
>>
>>> 2.   If it is determined that not enough blockers are fixed, does
>>> this mean that a 3.2 version of XUL will be made available and XUL will not
>>> be removed until 3.3
>>>
>>> Yes, if the core developers vote not to proceed with XUL removal, it
>> would be delayed until the next release cycle (3.3).
>>
>> Just to offer some perspective, from the dev side it's not just a
>> question of how many web staff blockers remain, but how much work is
>> required to resolve each, who can sign up to fix them, how many sites they
>> likely affect, how much developer time will be siphoned away from fixing
>> these issues trying to maintain XUL in 3.2 (!), the fact the XUL is already
>> a little bit broken in 3.2 based on the agreement it would it would be
>> removed, etc, etc.
>>
>> Thanks,
>>
>> -b
>>
>>
>>

Re: [OPEN-ILS-GENERAL] Bills Paid by Staff Login

[Mike Rylander]

Hi Elizabeth,

The cash reports are focused on the workstation, not the staff member, and
they include only cash, check and credit card payments made at a
workstation.  The Brick-and-mortar source includes account adjustments, as
well as forgive, credit (not credit card, but patron credit), work, and
goods payments.  You may want to consider using the Payment: Desk source,
which includes only the same payment types as the cash reports.

HTH,

--
Mike Rylander
 | Executive Director
 | Equinox Open Library Initiative
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  mi...@equinoxinitiative.org
 | web:  http://equinoxinitiative.org


On Tue, Aug 28, 2018 at 4:03 PM Elizabeth Davis  wrote:

> Hi Scott and Mike
>
>
>
> I have been testing the Payments: Brick-and-mortar source and comparing it
> to the Cash Reports and the cash totals do not seem to be matching.  Is
> anyone familiar with this?
>
>
>
>
>
> Elizabeth Davis
>
> Head of Digital Services
>
> Scranton Public Library
>
> 500 Vine Street
>
> Scranton, PA 18509
>
> 570-348-3000 ext. 3050
>
> eda...@albright.org
>
>
>
>
>
>
>
> *From:* Open-ils-general [mailto:
> open-ils-general-boun...@list.georgialibraries.org] *On Behalf Of *Mike
> Rylander
> *Sent:* Tuesday, August 28, 2018 9:59 AM
> *To:* Evergreen Discussion Group <
> open-ils-general@list.georgialibraries.org>
> *Subject:* Re: [OPEN-ILS-GENERAL] Bills Paid by Staff Login
>
>
>
> Hi Scott,
>
>
>
> In addition to what Bill mentions, the Accepting Staff Member field of the
> "Payments: Brick-and-mortar" links to the staff user that was logged in at
> the workstation where the payment was accepted.  That can be used to report
> exactly on how much money a staff member took in.
>
>
>
> HTH,
>
>
> --
> Mike Rylander
>  | Executive Director
>  | Equinox Open Library Initiative
>  | phone:  1-877-OPEN-ILS (673-6457)
>  | email:  mi...@equinoxinitiative.org
>  | web:  http://equinoxinitiative.org
>
>
>
>
>
> On Tue, Aug 28, 2018 at 8:14 AM Joan Kranich  wrote:
>
> Hi Scott,
>
>
>
> CW MARS has a few Payment report sources we use and one of our reports is
> by login.
>
>
>
> Joan
>
>
>
> On Tue, Aug 28, 2018 at 7:52 AM, Bill Ott  wrote:
>
> Check out: Administration > Local Administration > Cash Reports
>
> That will give you daily summaries (or whatever days you select). If
> you're looking for more detail, then a custom report may be in order.
>
>
>
> On 8/27/18 3:14 PM, scott.tho...@sparkpa.org wrote:
>
> We just migrated a library that is very strict about reporting out revenue
> collected by individual staff members at the Circulation Desk. Their
> previous ILS was able to output bill payments by staff login, but there is
> apparently no reporting source for this in Evergreen. First of all, is
> there a reporting source for this in Evergreen that we just haven’t found?
> If not, has anyone found a workaround for this?
>
>
>
> Thank you,
>
> Scott
>
>
>
> Scott Thomas
>
> Executive Director
>
> *PaILS / SPARK*
>
> (717) 873-9461
>
> scott.tho...@sparkpa.org
>
> Stay informed! Join the SPARK-User Email List:
>
> https://mail.palibrary.org/mailman/listinfo/spark-users
>
> [image: Description: Description: Training | SPARK – Pennsylvania's
> Statewide Library System] 
>
>
>
>
>
>
>
> --
>
> ​​
>
> Joan Kranich | Member Services Supervisor
>
> CW MARS
>
> jkran...@cwmars.org
>
> 508-755-3323 x321 or x1 <(508)%20755-3323>
>
> http://www.cwmars.org
>
>
>
>

Re: [OPEN-ILS-GENERAL] Bills Paid by Staff Login

[Elizabeth Davis]

Hi Scott and Mike

I have been testing the Payments: Brick-and-mortar source and comparing it to 
the Cash Reports and the cash totals do not seem to be matching.  Is anyone 
familiar with this?


Elizabeth Davis
Head of Digital Services
Scranton Public Library
500 Vine Street
Scranton, PA 18509
570-348-3000 ext. 3050
eda...@albright.org



From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Mike 
Rylander
Sent: Tuesday, August 28, 2018 9:59 AM
To: Evergreen Discussion Group 
Subject: Re: [OPEN-ILS-GENERAL] Bills Paid by Staff Login

Hi Scott,

In addition to what Bill mentions, the Accepting Staff Member field of the 
"Payments: Brick-and-mortar" links to the staff user that was logged in at the 
workstation where the payment was accepted.  That can be used to report exactly 
on how much money a staff member took in.

HTH,

--
Mike Rylander
 | Executive Director
 | Equinox Open Library Initiative
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  mi...@equinoxinitiative.org
 | web:  http://equinoxinitiative.org


On Tue, Aug 28, 2018 at 8:14 AM Joan Kranich 
mailto:jkran...@cwmars.org>> wrote:
Hi Scott,

CW MARS has a few Payment report sources we use and one of our reports is by 
login.

Joan

On Tue, Aug 28, 2018 at 7:52 AM, Bill Ott mailto:b...@grpl.org>> 
wrote:

Check out: Administration > Local Administration > Cash Reports

That will give you daily summaries (or whatever days you select). If you're 
looking for more detail, then a custom report may be in order.


On 8/27/18 3:14 PM, scott.tho...@sparkpa.org 
wrote:
We just migrated a library that is very strict about reporting out revenue 
collected by individual staff members at the Circulation Desk. Their previous 
ILS was able to output bill payments by staff login, but there is apparently no 
reporting source for this in Evergreen. First of all, is there a reporting 
source for this in Evergreen that we just haven’t found? If not, has anyone 
found a workaround for this?

Thank you,
Scott

Scott Thomas
Executive Director
PaILS / SPARK
(717) 873-9461
scott.tho...@sparkpa.org
Stay informed! Join the SPARK-User Email List:
https://mail.palibrary.org/mailman/listinfo/spark-users
[Description: Description: Training | SPARK –  Pennsylvania's 
Statewide Library System]




--
​​
[https://lh5.googleusercontent.com/C1fNrKOLEXFs-jfAIXQIMqbKqVBCJrBceOenfgotAcJE6XtZ2ZeeTYFkyfir63-HfzjX6q5zhBQWiO5RZk2tYnWzJ1_rjAADAH4nCmiuhNJuoG8HZLq7MBW-pAU4R9ScKcCybdVO]


Joan Kranich | Member Services Supervisor

CW MARS

jkran...@cwmars.org

508-755-3323 x321 or x1

http://www.cwmars.org

Re: [OPEN-ILS-GENERAL] Please help schedule our next Student Success WG meeting

[Jane Sandberg]

Hello all,

A friendly reminder to fill out this poll by the end of day Friday to
help schedule the Student Success WG meeting:
https://doodle.com/poll/4yup8a4cxwy53uk4

Thanks to all who have already voted.

On Fri, Aug 17, 2018 at 7:03 AM, Jane Sandberg  wrote:
> Hi Evergreeners,
>
> The Student Success Working Group is scheduling its Fall 2018 meeting.
> If you're interested in attending, please fill out this poll by the
> end of day on August 31st: https://doodle.com/poll/4yup8a4cxwy53uk4
>
> Student Success Working Group meetings are open to everybody, and have
> a particular focus on libraries that serve students at the primary,
> secondary, and post-secondary levels.  You can learn more about our
> current priorities and areas of interest here:
> https://wiki.evergreen-ils.org/doku.php?id=student_success_working_group
>
>-Jane
>
> --
> Jane Sandberg
> Electronic Resources Librarian
> Linn-Benton Community College
> sand...@linnbenton.edu / 541-917-4655
> Pronouns: she/her/hers



-- 
Jane Sandberg
Electronic Resources Librarian
Linn-Benton Community College
sand...@linnbenton.edu / 541-917-4655
Pronouns: she/her/hers

[OPEN-ILS-GENERAL] Evergreen Community Bug Squashing Week: September 10-14

[Terran McCanna]

 Hello everyone,

Our next community-wide Bug Squashing Week is scheduled for Monday,
September 10 through Friday, September 14.

(Don't worry, you don't need to set aside the entire week to
participate - you can participate however much that you can fit into
your schedule!)

You may participate in Bug Squashing Day by:

- Submitting new bug fixes for reported bugs
- Testing bug fixes that others have submitted (these should have the
"pullrequest" tag)
- Confirming bug reports that haven't been reviewed yet (this is a
great way to participate if you're not a coder!)
- Pushing bug fixes into Evergreen (for core committers)
- Assisting with documentation updates

Bug Squashing Day Info and Guidelines:
http://wiki.evergreen-ils.org/doku.php?id=dev:bug_squashing

If you would like to request a sandbox to test bug fixes on please
fill out the this form:
http://bit.ly/2tMCXiD


Please let me know if you have any questions.

Thank you!

Terran McCanna
PINES Program Manager
Georgia Public Library Service
tmcca...@georgialibraries.org

* The GPLS office is in the midst of relocating offices. We may be reached
by all of the current mechanisms during the transition, but to ensure the
most prompt response, please use the Help Desk:
https://help.georgialibraries.org

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] 3.2 feature freeze and more

[Kathy Lussier]

Hi Bill,

In looking at the list of showstoppers, I see one has a pullrequest, so it
seems reasonable it could be tested and merged soon. For the other bugs,
does anyone have a sense of whether any are particularly complex? Or are
they mostly straightforward bugs that just haven't been addressed yet due
to lack of tuits? If it's the latter, could we consider delaying the full
release (with xul removal) until the showstoppers are fixed?

I'm concerned about the breakage that is likely to occur the longer we
continue to make the xul client available in our releases, but these bugs
were identified as real issues in getting libraries to adopt the web
client. At this time, there are just a handful of remaining showstoppers,
and if we can commit to getting them resolved before the full release, I
think it will make a smoother transition to 3.2 for our libraries.

Kathy

-- 
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128kluss...@masslnc.org



On Mon, Aug 27, 2018 at 6:47 PM Bill Erickson  wrote:

> Hi Scott,
>
> On Mon, Aug 27, 2018 at 5:24 PM scott.tho...@sparkpa.org <
> scott.tho...@sparkpa.org> wrote:
>
>> Hi Bill,
>>
>> I have two questions about this:
>>
>>
>>
>> 1.   You mentioned a vote. Who is the “we” that votes?
>>
> Good question.  This would be a core developer vote.   I started typing
> this as a developer list message, then added the general list just before
> sending...
>
> From my perspective, this vote is more about getting a public record of
> developer buy-in (or otherwise) as is typically the case before proceeding
> with a large architectural change.  It also acts as a "should we do this?"
> safety valve.  However, I call the vote now because in my opinion as RM we
> are ready to proceed and I suspect that's what we'll decide.  It's not done
> 'til it's done, though.
>
> It's also worth reminding everyone we are also providing extended support
> for Evergreen 3.1, so users can continue using the XUL client for a longer
> period of time.  Normally, a release is supported for 12 months of bug
> fixes, plus 3 months of security fixes.  3.1 will be supported for a longer
> period of time -- duration TBD -- so sites will have more time before
> needing to upgrade to 3.2.  This will buy us more time in the community to
> continue squashing bugs as well.
>
>> 2.   If it is determined that not enough blockers are fixed, does
>> this mean that a 3.2 version of XUL will be made available and XUL will not
>> be removed until 3.3
>>
>> Yes, if the core developers vote not to proceed with XUL removal, it
> would be delayed until the next release cycle (3.3).
>
> Just to offer some perspective, from the dev side it's not just a question
> of how many web staff blockers remain, but how much work is required to
> resolve each, who can sign up to fix them, how many sites they likely
> affect, how much developer time will be siphoned away from fixing these
> issues trying to maintain XUL in 3.2 (!), the fact the XUL is already a
> little bit broken in 3.2 based on the agreement it would it would be
> removed, etc, etc.
>
> Thanks,
>
> -b
>
>
>

Re: [OPEN-ILS-GENERAL] Bills Paid by Staff Login

[Mike Rylander]

Hi Scott,

In addition to what Bill mentions, the Accepting Staff Member field of the
"Payments: Brick-and-mortar" links to the staff user that was logged in at
the workstation where the payment was accepted.  That can be used to report
exactly on how much money a staff member took in.

HTH,

--
Mike Rylander
 | Executive Director
 | Equinox Open Library Initiative
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  mi...@equinoxinitiative.org
 | web:  http://equinoxinitiative.org


On Tue, Aug 28, 2018 at 8:14 AM Joan Kranich  wrote:

> Hi Scott,
>
> CW MARS has a few Payment report sources we use and one of our reports is
> by login.
>
> Joan
>
> On Tue, Aug 28, 2018 at 7:52 AM, Bill Ott  wrote:
>
>> Check out: Administration > Local Administration > Cash Reports
>>
>> That will give you daily summaries (or whatever days you select). If
>> you're looking for more detail, then a custom report may be in order.
>>
>>
>> On 8/27/18 3:14 PM, scott.tho...@sparkpa.org wrote:
>>
>> We just migrated a library that is very strict about reporting out
>> revenue collected by individual staff members at the Circulation Desk.
>> Their previous ILS was able to output bill payments by staff login, but
>> there is apparently no reporting source for this in Evergreen. First of
>> all, is there a reporting source for this in Evergreen that we just haven’t
>> found? If not, has anyone found a workaround for this?
>>
>>
>>
>> Thank you,
>>
>> Scott
>>
>>
>>
>> Scott Thomas
>>
>> Executive Director
>>
>> *PaILS / SPARK*
>>
>> (717) 873-9461
>>
>> scott.tho...@sparkpa.org
>>
>> Stay informed! Join the SPARK-User Email List:
>>
>> https://mail.palibrary.org/mailman/listinfo/spark-users
>>
>> [image: Description: Description: Training | SPARK – Pennsylvania's
>> Statewide Library System] 
>>
>>
>>
>>
>
>
> --
>
> ​​
>
> Joan Kranich | Member Services Supervisor
>
> CW MARS
>
> jkran...@cwmars.org
>
> 508-755-3323 x321 or x1 <(508)%20755-3323>
>
> http://www.cwmars.org
>
>

Re: [OPEN-ILS-GENERAL] Bills Paid by Staff Login

[Joan Kranich]

Hi Scott,

CW MARS has a few Payment report sources we use and one of our reports is
by login.

Joan

On Tue, Aug 28, 2018 at 7:52 AM, Bill Ott  wrote:

> Check out: Administration > Local Administration > Cash Reports
>
> That will give you daily summaries (or whatever days you select). If
> you're looking for more detail, then a custom report may be in order.
>
>
> On 8/27/18 3:14 PM, scott.tho...@sparkpa.org wrote:
>
> We just migrated a library that is very strict about reporting out revenue
> collected by individual staff members at the Circulation Desk. Their
> previous ILS was able to output bill payments by staff login, but there is
> apparently no reporting source for this in Evergreen. First of all, is
> there a reporting source for this in Evergreen that we just haven’t found?
> If not, has anyone found a workaround for this?
>
>
>
> Thank you,
>
> Scott
>
>
>
> Scott Thomas
>
> Executive Director
>
> *PaILS / SPARK*
>
> (717) 873-9461
>
> scott.tho...@sparkpa.org
>
> Stay informed! Join the SPARK-User Email List:
>
> https://mail.palibrary.org/mailman/listinfo/spark-users
>
> [image: Description: Description: Training | SPARK – Pennsylvania's
> Statewide Library System] 
>
>
>
>


-- 

​​

Joan Kranich | Member Services Supervisor

CW MARS

jkran...@cwmars.org

508-755-3323 x321 or x1 <(508)%20755-3323>

http://www.cwmars.org

Re: [OPEN-ILS-GENERAL] Bills Paid by Staff Login

[Bill Ott]

Check out: Administration > Local Administration > Cash Reports

That will give you daily summaries (or whatever days you select). If 
you're looking for more detail, then a custom report may be in order.



On 8/27/18 3:14 PM, scott.tho...@sparkpa.org wrote:


We just migrated a library that is very strict about reporting out 
revenue collected by individual staff members at the Circulation Desk. 
Their previous ILS was able to output bill payments by staff login, 
but there is apparently no reporting source for this in Evergreen. 
First of all, is there a reporting source for this in Evergreen that 
we just haven’t found? If not, has anyone found a workaround for this?


Thank you,

Scott

Scott Thomas

Executive Director

*PaILS / SPARK*

(717) 873-9461

scott.tho...@sparkpa.org 

Stay informed! Join the SPARK-User Email List:

https://mail.palibrary.org/mailman/listinfo/spark-users

Description: Description: Training | SPARK – Pennsylvania's Statewide 
Library System