From klussier at masslnc.org  Wed Nov  8 11:30:13 2017
From: klussier at masslnc.org (Kathy Lussier)
Date: Wed, 8 Nov 2017 11:30:13 -0500
Subject: [Evergreen-acq] Fwd: [OPEN-ILS-GENERAL] Project to move
	acquisitions to AngularJS
In-Reply-To: <fd056771-0418-d4f3-929b-55f78d7a83f0@masslnc.org>
References: <fd056771-0418-d4f3-929b-55f78d7a83f0@masslnc.org>
Message-ID: <7c324f56-9679-c4db-b3d2-fdaf92755b28@masslnc.org>

Hi all,

I posted this message to the general list a few weeks ago for maximum 
visibility, but I'm forwarding it along to this list too to make sure 
all the acq folks have seen it. Feel free to add comments and 
suggestions to our Google doc!

Kathy



-------- Forwarded Message --------
Subject: 	[OPEN-ILS-GENERAL] Project to move acquisitions to AngularJS
Date: 	Fri, 27 Oct 2017 07:15:49 -0400
From: 	Kathy Lussier <klussier at masslnc.org>
Reply-To: 	Evergreen Discussion Group 
<open-ils-general at list.georgialibraries.org>
To: 	'Evergreen Discussion Group' 
<open-ils-general at list.georgialibraries.org>



Hi all,

I originally was going to post this to the acq list, but I decided to 
post here for maximum visibility.

Although the web client is officially available for production use in 
3.0, we still have many interfaces, built in Dojo, that were ported over 
as is. Moving these interfaces over helped us make the web client 
available to libraries sooner than we could have done otherwise, but I'm 
hoping we can keep momentum going and gradually move all of the Dojo 
interfaces over the Angular.

The MassLNC Evergreen Development Initiative partners would like to 
start this process with the acquisitions interfaces. Our development 
committee has agreed to commit some funding this fiscal year to moving 
acquisitions to Angular. We have three goals for this project:

- As was the case with the original web client project, we would be 
focusing on feature parity in Angular, except where noted below. 
Although there are several bugs that have been reported in acquisitions 
as well as requests for new features, this isn't a project to fix of all 
of our acquisitions issues.

- Having said that, we see a move to AngularJS as an opportunity to make 
some tweaks to the UI that will improve the use of acquisitions for our 
staff. By tweaks, I mean making some settings sticky that previously 
required constant adjustment; improve listing and paging of acq 
elements; adding fields to some displays; and tinkering with some search 
options. I'm aware that some of these UI tweaks may also require some 
backend tweaking, but we aren't looking to do any major backend changes 
under this goal.

- We also would like to improve sorting in the admin interfaces and add 
sorting for line items in the line item search results, selection list, 
PO, and invoice interfaces. Although it may seem as if sorting falls in 
the category of UI tweaks, based on previous discussions I've had with 
developers, this work will probably require enough backend work to push 
it out of the tweak category. Nevertheless, the call for sorting in 
these interfaces has been so strong over the years that we think it 
really needs to be done as part of the transition.

I've worked with the MassLNC development partners (C/W MARS, NOBLE, 
Bibliomation, Sitka, Georgia PINES, Evergreen Indiana and LARL/NWRL) to 
come up with draft requirements for this project. 
https://docs.google.com/document/d/1lvf0MZaTgT4r59EU8WAnt2g60Q_MFKb9x8hUZZOa8Xw/edit?usp=sharing

The intent of the requirements document is not to describe all of the 
behavior of all acq interfaces. The underlying assumption is that we 
want feature parity in each interface. However, I do describe some 
existing behavior that I want to make sure does not get overlooked. Any 
new behavior is highlighted in the document in green, bold font.

At this time, we're looking for the following:

*Acquisitions folks *- if you have any feedback on these requirements, 
let us know. Anyone using the link to the Google doc can make comments 
or suggested edits on the document. However, please remember that we're 
trying to limit this project to UI tweaks, not major new functionality 
or redesigned interfaces.

*Developers *- If you see any 'UI tweaks' that really are features 
requiring extensive backend changes, please let us know. In particular, 
at the bottom of the document (III)(F)(3) we have some requested 
acquisitions search options that I was unsure about. Also, in the line 
items section where we request sorting (III)(A)(2), if there is a 
particular sort field that raises red flags for you for being able to 
sort it in a performant manner, let us know.

*Potential funders *- I anticipate this will be a large project, but, in 
order to get the web client to where it needs to be, we need to keep 
Angularizing these older interfaces. As was the case of with the initial 
web client project, we're going to need funding contributions from 
throughout the community to proceed with this project. We have not yet 
sought a quote for this work and, therefore, do not know what the cost 
will be. However, if your organization can commit funding to this 
project (we don't need a number yet), please contact me directly so that 
you can be part of the project from the outset.

Feel free to let me know if you have any questions!

Kathy

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-acq/attachments/20171108/281da9fb/attachment.html>

From tlittle at georgialibraries.org  Thu Nov 16 10:19:08 2017
From: tlittle at georgialibraries.org (Tiffany Little)
Date: Thu, 16 Nov 2017 10:19:08 -0500
Subject: [Evergreen-acq] Training Acquisitions
Message-ID: <CABT_fJxr+GDm9MDFddhXc78DbGiHjZAyeGMiV4krVsNvDBM18Q@mail.gmail.com>

Good morning everyone,

For anyone out there who trains others on Acquisitions, do you have any
training materials that you're inclined to share? Outlines, talking points,
tips, whatever? I'm always interested in seeing what others do and if I can
improve mine.

Thanks!
Tiffany

--
Tiffany Little
*PINES Services Specialist, Acquisitions*
Georgia Public Library Service
1800 Century Place NE, Suite 150
Atlanta, Georgia 30345
(404) 235-7161
tlittle at georgialibraries.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-acq/attachments/20171116/ea06cf03/attachment.html>

From jamundson at cwmars.org  Thu Nov 16 15:09:53 2017
From: jamundson at cwmars.org (John Amundson)
Date: Thu, 16 Nov 2017 15:09:53 -0500
Subject: [Evergreen-acq] Training Acquisitions
In-Reply-To: <CABT_fJxr+GDm9MDFddhXc78DbGiHjZAyeGMiV4krVsNvDBM18Q@mail.gmail.com>
References: <CABT_fJxr+GDm9MDFddhXc78DbGiHjZAyeGMiV4krVsNvDBM18Q@mail.gmail.com>
Message-ID: <CAKdkULF1onxvm2rdNnvDL=K05b+2ia6OAS=vpkBYFkSgDAfBWQ@mail.gmail.com>

Hi, Tiffany:

I've attached C/W MARS' Initial Acquisitions Documentation. I created them
to send out to libraries considering Evergreen Acquisitions. The First Look
document is intended to help libraries choose a level of Acquisitions, and
the Preparing For... docs are intended to be sent out to libraries before
the first training session. The idea is that these will help staff with the
transition to the Acquisitions function and the lingo it uses, (Fund Codes,
Providers, etc). Along with the appropriate prep doc, I will also send a
list of the library's shelving locations and circ modifiers so that they
can begin setup on the vendor's side, as well.

We haven't had much of a chance to use them in the wild yet, but the two
libraries that we have trained with some version of documents thought they
were helpful.

I think a lot of the contents are C/W MARS specific, but maybe there's some
material in there from which you can take inspiration!

John

*John Amundson*
Library Applications Associate III
C/W MARS, Inc.
jamundson at cwmars.org
(508) 755-3323 ext 322

On Thu, Nov 16, 2017 at 10:19 AM, Tiffany Little <
tlittle at georgialibraries.org> wrote:

> Good morning everyone,
>
> For anyone out there who trains others on Acquisitions, do you have any
> training materials that you're inclined to share? Outlines, talking points,
> tips, whatever? I'm always interested in seeing what others do and if I can
> improve mine.
>
> Thanks!
> Tiffany
>
> --
> Tiffany Little
> *PINES Services Specialist, Acquisitions*
> Georgia Public Library Service
> 1800 Century Place NE, Suite 150
> Atlanta, Georgia 30345
> (404) 235-7161
> tlittle at georgialibraries.org
>
> _______________________________________________
> Evergreen-acq mailing list
> Evergreen-acq at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-acq
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-acq/attachments/20171116/c829f3ff/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Copy of C%2FW MARS - Preparing for Evergreen Acquisitions - Fund Tracking (1).pdf
Type: application/pdf
Size: 164820 bytes
Desc: not available
URL: <http://list.evergreen-ils.org/pipermail/evergreen-acq/attachments/20171116/c829f3ff/attachment-0004.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Copy of C%2FW MARS - Preparing for Evergreen Acquisitions - Order Only (1).pdf
Type: application/pdf
Size: 149005 bytes
Desc: not available
URL: <http://list.evergreen-ils.org/pipermail/evergreen-acq/attachments/20171116/c829f3ff/attachment-0005.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Copy of C%2FW MARS - Preparing for Evergreen Acquisitions -  EDI (1).pdf
Type: application/pdf
Size: 175376 bytes
Desc: not available
URL: <http://list.evergreen-ils.org/pipermail/evergreen-acq/attachments/20171116/c829f3ff/attachment-0006.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Copy of C%2FW MARS - Evergreen Acquisitions First Look.pdf
Type: application/pdf
Size: 152811 bytes
Desc: not available
URL: <http://list.evergreen-ils.org/pipermail/evergreen-acq/attachments/20171116/c829f3ff/attachment-0007.pdf>

From christine.burns at bc.libraries.coop  Fri Nov 24 19:02:29 2017
From: christine.burns at bc.libraries.coop (Christine Burns)
Date: Fri, 24 Nov 2017 16:02:29 -0800
Subject: [Evergreen-acq] November Acquisitions Bug of the Month
Message-ID: <9050f5bd-177f-70c2-51dc-f13c66ffe32d@bc.libraries.coop>

Hello

Here is the November Acquisitions Bug of the Month.

*Bug *- Uploading and activating orders with an inactive fund should not 
be possible
https://bugs.launchpad.net/evergreen/+bug/1347090

*Description of Bug*
If you upload order records with inactive funds entered in the holdings 
tag (or, perhaps, select the wrong fiscal year in the order upload form) 
the records will successfully upload and activate.

*Evergreen Version(s)*
EG 2.8 +

*Desired Resolution / Fix*
Ideally, after the user clicks upload, if the system saw that any line 
items had an inactive fund, the upload would fail with a message 
informing the user what the problem is.

*Linked / Related / Duplicate bugs*
https://bugs.launchpad.net/evergreen/+bug/924952

Thank you to Kathy Lussier for suggesting this month?s Bug

Get involved by testing your system for the bug, indicating on Launchpad 
if you?re affected by the bug, and commenting on Launchpad or through 
the list if you have further information about the bug or suggestions 
about what you?d like to see in a fix.

Have a bug you?d like to see featured as an Acquisitions Bug of the 
Month?? Please email a link to the launchpad bug # to 
jennifer.pringle at bc.libraries.coop.

Thank you

Christine

-- 
Christine Burns
Co-op Support
BC Libraries Cooperative
Ph: 1-888-848-9250
https://bc.libraries.coop
https://status.libraries.coop/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-acq/attachments/20171124/452e5428/attachment.html>