| Time |
Nick |
Message |
| 02:21 |
|
JBoyer joined #evergreen |
| 07:03 |
|
sleary joined #evergreen |
| 07:15 |
|
kworstell-isl joined #evergreen |
| 07:54 |
|
collum joined #evergreen |
| 08:04 |
|
BDorsey joined #evergreen |
| 08:09 |
|
rfrasur joined #evergreen |
| 08:10 |
|
PhilMakesStuff joined #evergreen |
| 08:11 |
PhilMakesStuff |
This is a test message to see if I am posting in the correct channel |
| 08:12 |
PhilMakesStuff |
Quick question: I was wondering if evergreen has a Voluntary Product Accessibility Template (VPAT)? |
| 08:13 |
PhilMakesStuff |
We will need this in order for our organization to use Evergreen |
| 08:23 |
JBoyer |
Hi PhilMakesStuff , that sounds familiar but you may have more luck getting responses on the Evergreen general email lists as IRC activity is pretty irregular. |
| 08:25 |
PhilMakesStuff |
Thanks. Will try that. |
| 08:37 |
|
sleary joined #evergreen |
| 08:42 |
|
mmorgan joined #evergreen |
| 08:55 |
|
Christineb joined #evergreen |
| 09:10 |
|
Dyrcona joined #evergreen |
| 10:48 |
|
sandbergja joined #evergreen |
| 10:53 |
|
collum joined #evergreen |
| 10:53 |
sandbergja |
I am curious about a behavior in the AngularJS patron notes. If you create a note with a block, and then the patron reads it, the staff member can no longer edit or delete the note. You can archive it, which removes the block but leaves the message for the patron in the OPAC. |
| 10:54 |
sandbergja |
I wanted to learn more about the motivation here -- why we don't allow staff members to delete or edit after the patron has read them. I also wanted to know if folks feel that it is working well at the circ desk, or if circ staff at your libraries would like the ability to delete/edit these. |
| 10:57 |
csharp_ |
sandbergja: without any data to support it, my take is that staff should be able to control those, perhaps under the control of permissions so not just anyone can? |
| 11:09 |
|
collum joined #evergreen |
| 11:57 |
mmorgan |
re: sandbergja's question about the patron notes, I'm just guessing on the motivation, but if the patron deletes the message, the staff can then remove it. Maybe the idea is staff should not deleted it if the patron has read it and has chosen to keep it rather than delete it? |
| 11:58 |
mmorgan |
If then patron then goes back and deletes their message, staff have the option to delete - unless they have already archived it. |
| 11:59 |
|
sandbergja joined #evergreen |
| 12:00 |
sandbergja |
csharp_++ |
| 12:00 |
sandbergja |
mmorgan++ |
| 12:01 |
mmorgan |
IMO the notes interfaces in AngularJS are kind of unwieldy, likely because the three different notes/alerts/messages tables were merged. |
| 12:02 |
sandbergja |
Yeah, it does have a ton of capabilities in a very small space for sure. |
| 12:02 |
sandbergja |
I wonder if a confirmation alert for staff would meet the same presumed motivation. Like when you try to edit it: "The patron has already read this message, editing it may lead to confusion. Are you sure?" |
| 12:03 |
|
jihpringle joined #evergreen |
| 12:03 |
sandbergja |
While still giving the ability for staff to delete/edit a note after working something out with a patron. |
| 12:08 |
* mmorgan |
would agree that staff should be able to delete a message, even if it has been read, with at least fair warning. |
| 12:34 |
|
collum joined #evergreen |
| 12:45 |
|
collum joined #evergreen |
| 12:50 |
|
dmoore_doppel joined #evergreen |
| 12:56 |
|
sleary joined #evergreen |
| 13:04 |
|
jihpringle joined #evergreen |
| 13:41 |
|
javier_guel joined #evergreen |
| 13:42 |
javier_guel |
Hi all, I am trying to upgrade EG version, and I am on the db upgrade scripts, but I can´t find the 3.7.4 to any version and it doesnt exist |
| 13:42 |
javier_guel |
it is just 3.7.3-3.7.4-upgrade-db.sql and then 3.8.0-3.8.1-upgrade-db.sql but not the other one |
| 13:54 |
sleary |
FYI, UI interest group getting started in about 5 minutes: https://meet.google.com/avm-hdae-awu |
| 13:56 |
JBoyer |
javier_guel, this is somewhere we could stand do improve some processes; If you upgraded beyond 3.7.1 you can't use the version-upgrade scripts to go to 3.8.0. You can use the individual sql upgrade scripts in the Open-ILS/src/sql/Pg/upgrade directory. You can compare what you have in your database (the config.upgrade_log table) to what the version-upgrade scripts would do. If you use grep to match '_deps' in the |
| 13:56 |
JBoyer |
version-upgrade scripts you'll get the list of numbered scripts that need to be run. |
| 14:09 |
javier_guel |
JBoyer: thanks, I wiil try that |
| 14:10 |
JBoyer |
javier_guel, Once you get to the point where none of the numbers in a version upgrade are in the db, you can switch back to running them if you prefer. |
| 14:24 |
|
Dyrcona joined #evergreen |
| 14:26 |
jeff |
our friend with the VPAT inquiry emailed us directly also. :-) |
| 14:27 |
Dyrcona |
I've never heard of it. |
| 14:27 |
Dyrcona |
Until today that is. |
| 14:28 |
Dyrcona |
javier_guel: If you're feeling adventurous and don't mind using git, you can use a script I wrote to make a db upgrade script to go between arbitrary versions: https://gist.github.com/Dyrcona/00bd6b6290b6fbbb579c7f93b360ab0d |
| 14:34 |
|
dmoore_doppel joined #evergreen |
| 16:00 |
javier_guel |
great thanks, i will try |
| 16:44 |
|
dmoore_doppel joined #evergreen |
| 16:59 |
|
mmorgan left #evergreen |
| 17:31 |
dmoore |
hey all - any thoughts on this API note published on EBSCO's Novelist page - https://connect.ebsco.com/s/article/Setting-up-On-The-Shelf?language=en_US |
| 17:32 |
dmoore |
"Note: There is an Evergreen API that supports automatic harvesting of your collection. However, we were unable to obtain a complete harvest for any customers during the testing of this functionality, as Evergreen’s Web Services API was not built for such a wide-scale application. We discourage Evergreen customers from utilizing this feature for collection harvesting." |
| 17:32 |
csharp_ |
dmoore: we don't use it in PINES, but anecdotally, I've heard from sites who do that the harvesting can eat into available server resources |
| 17:33 |
berick |
hah, yeah, IIRC, they were madly spewing api calls |
| 17:33 |
csharp_ |
dmoore: we sent a monthly upload to NoveList so they can reference it offline |
| 17:33 |
csharp_ |
s/sent/send |
| 17:33 |
csharp_ |
\/ |
| 17:33 |
csharp_ |
@who let the dogs out? |
| 17:33 |
pinesol |
akilsdonk let the dogs out. |
| 17:34 |
berick |
indeed they let loose the dogs of war |
| 17:35 |
csharp_ |
"WHATEVER farm animal of war, Lana" |
| 17:36 |
dmoore |
i'm gonna send this out over the listserv for some community wisdom... we're looking into implementing it and are torn between the API vs. upload route |
| 17:36 |
csharp_ |
upload upload (everybody) upload! |
| 17:38 |
berick |
just, wow, "it's evergreen's fault" |
| 17:38 |
berick |
*sigh* |
| 17:38 |
csharp_ |
nobody likes them anyway :-) |
| 17:38 |
dmoore |
right? so rude. |
| 17:39 |
|
sleary_ joined #evergreen |
| 17:39 |
dmoore |
"evergreen's just awful so switch ILS's then use Novelist" |
| 17:40 |
csharp_ |
use FOLIO! it's Open Source™! |
| 17:41 |
* csharp_ |
shouldn't snark :-/ |
| 17:48 |
|
sleary joined #evergreen |
| 18:34 |
|
jihpringle joined #evergreen |
| 18:57 |
|
dmoore_doppel joined #evergreen |
