Time |
Nick |
Message |
00:36 |
|
Guest78532 left #evergreen |
07:41 |
|
ericar joined #evergreen |
07:48 |
|
mrpeters joined #evergreen |
07:54 |
|
rjackson_isl joined #evergreen |
07:55 |
|
jboyer-isl joined #evergreen |
08:06 |
|
collum joined #evergreen |
08:27 |
|
Dyrcona joined #evergreen |
08:48 |
|
mmorgan joined #evergreen |
09:06 |
|
maryj joined #evergreen |
09:08 |
|
RoganH joined #evergreen |
09:28 |
|
mmorgan joined #evergreen |
09:38 |
|
jwoodard joined #evergreen |
09:38 |
|
yboston joined #evergreen |
10:49 |
|
_bott_ joined #evergreen |
11:04 |
csharp |
is anyone out there using PayPal (not PayFlow Pro) for fines/fee payment within EG? |
11:04 |
csharp |
we're having a devil of a time figuring out what's needed and PayPal support is pretty lacking so far |
11:06 |
tsbere |
csharp: We are not, but I have set up paypal elsewhere before. |
11:07 |
csharp |
we're currently getting the message: "10501: This transaction cannot be processed due to an invalid merchant configuration." |
11:09 |
csharp |
ah - I found the docs on that error here: https://developer.paypal.com/docs/classic/api/errorcodes/ |
11:09 |
csharp |
rubber_ducking++ |
11:09 |
csharp |
we'll see where we can go from there |
11:10 |
tsbere |
csharp: For note, I had a lot of trouble when setting something up when the person had a token on their account, had to use alternate credentials but I forget how we got them. |
11:26 |
|
Christineb joined #evergreen |
11:27 |
|
mmorgan joined #evergreen |
11:47 |
mmorgan |
csharp: We are working through the same issues with paypal. I got that same error and tracked it to needing to upgrade to a "Pro" account. |
11:48 |
mmorgan |
We have been working in a sandbox so far and upgrading to a pro account in a sandbox can be done with just a click on PayPal's developer site. under Accounts. I can dig further as to exactly where, if it helps. |
11:48 |
csharp |
mmorgan: thanks! I'll look into that as a possible cause, because we appear to have all the auth bits in the right place |
11:49 |
csharp |
mmorgan: amazing - we've been asking paypal about access to a sandbox and they seem to have no idea what we're talking about :-/ |
11:49 |
csharp |
our experience with their merchant-side customer service has been less than stellar |
11:50 |
mmorgan |
We actually never asked PayPal anything about setup for Evergreen. We've figured out what we have so far by poking. |
11:51 |
csharp |
mmorgan++ |
11:52 |
mmorgan |
Our Admin assistant set up the paypal account, but we found the credentials got us into https://developer.paypal.com |
11:53 |
mmorgan |
Once in, there's a Dashboard link that has info on Sandbox accounts. |
11:58 |
mmorgan |
We found a "facilitator" and a "buyer" sandbox account already existed. On the facilitator account profile, we found the Upgrade to Pro button. |
12:00 |
csharp |
mmorgan: I think the lack of a Pro account is the issue here. We're pretty sure the library will probably opt for Stripe since it's a lower monthly fee, but we may follow up with you on this to compare notes |
12:00 |
csharp |
mmorgan: will you be at the Hackaway next week? |
12:01 |
mmorgan |
Yes, since it's steps from my desk :) |
12:01 |
berick |
heh |
12:02 |
mmorgan |
Looking forward to learning a lot! |
12:02 |
|
bmills joined #evergreen |
12:09 |
csharp |
mmorgan: excellent - maybe we can compare notes in person (if the library still wants to) ;-) |
12:10 |
mmorgan |
csharp: For sure! |
12:24 |
|
jihpringle joined #evergreen |
12:44 |
|
Dyrcona1 joined #evergreen |
13:39 |
kmlussier |
Bug wrangling question. |
13:40 |
kmlussier |
It appears as if bug 1086934 made it in for 2.9.beta, but we forgot to move it to Fix Committed, so the milestone was updated to 2.next. |
13:40 |
pinesol_green |
Launchpad bug 1086934 in Evergreen "TPAC: Complete column sorting in some screens" [Wishlist,Confirmed] https://launchpad.net/bugs/1086934 |
13:40 |
kmlussier |
I want to update the mileston, but my only option now is to move it to 2.9.1. Is there a way I can set the milestone, at this point, to 2.9.beta? |
13:46 |
* kmlussier |
also throws a link to some signedoff patches in case anyone is interested in merging some. http://bit.ly/1kNdEVP |
13:46 |
kmlussier |
Looks like there are a few tests there from our last testing day. |
14:11 |
Dyrcona |
kmlussier: I just took care of it. I made the 2.9-beta temporarily active to retarget the bug, then set it to fixed released. |
14:43 |
kmlussier |
Dyrcona++ # Thank you! |
14:45 |
ldw |
Has there ever been any work done on creating an OAI-PMH Repository for Evergreen? |
14:47 |
tsbere |
I don't think so, but I probably wouldn't have noticed if there had. |
14:48 |
|
jlitrell joined #evergreen |
15:01 |
|
bmills joined #evergreen |
15:48 |
jeff |
jboyer-isl++ for the following comment in his Ansible playbook: # The only place you can find a single core CPU these days is a dishwasher; your package is bad and you should feel bad |
15:55 |
berick |
suddenly very proud of my 8-core Bosch |
15:55 |
berick |
it's water cooled! |
15:55 |
jboyer-isl |
berick++ |
15:55 |
jeff |
berick++ |
16:08 |
miker |
ldw: unapi and supercat stand ready for an implementor with tag: URIs and various output formats ... but implementing oai-pmh seems overkill for inital priming of an external indexer, which AIUI is why no other external indexer does it that way (he says, based on context clues ;) ) |
16:12 |
miker |
ldw: fwiw, the reason I implemented the oai_dc format for supercat/unapi was to lower the bar for others |
16:14 |
ldw |
miker: It might be overkill, but I wonder if I was to try and write something to prime Solr via the EG db that I might miss something that OAI-PMH would have covered already. I suppose a full reading of the standard should make me aware of most gotchas. |
16:15 |
phasefx |
ldw: there was a process for dumping into XC Catalog for OAI-PMH stuff |
16:16 |
phasefx |
not sure the state of that project |
16:16 |
ldw |
phasefx: I took a quick look at XC Catalog today. I will do more research before the Hack-a-way. |
16:16 |
miker |
phasefx: officially, it's dead :( |
16:17 |
ldw |
:( |
16:17 |
miker |
(last I heard) |
16:17 |
* phasefx |
thought someone took it over, but it's practically dead |
16:18 |
phasefx |
smidge of activity on the [XC Developers] mailing list from February |
16:22 |
miker |
ldw: oai-pmh is not particularly hard to do ... wrap existing output in a special xml envelope for GetRecord, generate a list of headers for ListRecords (with resumption tokens via memcache). but it's also a slow way to move records en masse for large collections. priming is a rare thing, so solving real-time update (with ALL the info needed to implement everything that we do today, which is /not/ based solely on the MARC) is the real challenge on the |
16:22 |
miker |
EG side. then it's figuring out how to actually implement what we do in solr, which is not just search |
16:23 |
berick |
and don't forget https://github.com/solrmarc/solrmarc -- but yes, what miker said. MARC is the easy part here |
16:23 |
ldw |
miker: What other aspects do we need to consider besides MARC? |
16:24 |
dbs |
Yep, or the triggers that we used to enable artunit to build a solr-based search of the catalogue (with views on the most recently-updated records, etc) |
16:24 |
miker |
(and, note, TF-IDF is good for a single corpus. in an consortium, you're really dealing with many partially overlapping but divergent corpi, all with potentially different sets of filters/limiters/semantics) |
16:25 |
ldw |
dbs: what is artunit? |
16:25 |
miker |
ldw: item data, volume data, shelving locations, various "visibility" flags spread amongs many objects (including org units as a whole) |
16:25 |
dbs |
ldw: art rhyno, windsor librarian extraordinaire |
16:25 |
dbs |
(back when he was creating a bento box search) |
16:26 |
miker |
ldw: and that's really just OTTOMH ... there's more and subtler issues |
16:26 |
dbs |
parts! |
16:26 |
miker |
all that said, I'm for having the conversation |
16:26 |
dbs |
:) |
16:26 |
miker |
parts++ |
16:26 |
miker |
;) |
16:26 |
ldw |
miker: ok, I look forward to the conversation too. |
16:26 |
miker |
issuances (which can cross org unit boundaries) |
16:28 |
dbs |
http://git.mvlcstaff.org/?p=Evergreen/ILS-Contrib.git;a=commitdiff;h=e0a9eb851a1a30de25e1f63914810478a062502d was a bit of what I worked on way back when |
16:29 |
miker |
on a completely unrelated subject ... how do folks feel about pulling these into the web staff client: http://tamerayd.in/ngToast/# http://ngmodules.org/modules/angular-tree-control |
16:29 |
miker |
a toaster notification widget and a tree implementation (for report templates) |
16:30 |
dbs |
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbs/solr_sync might be the most complete iteration I ever did |
16:30 |
ldw |
dbs: thanks for the links. |
16:53 |
jwoodard |
just a question is the Sitka documentation the best go-to guide for evergreen? |
16:58 |
yboston |
I always forget to check the Sitka docs, but I hear very good things. I normally just use the offical docs. On occasion I have looked at Indiana docs and PINES docs |
17:06 |
|
mmorgan left #evergreen |
17:12 |
dbwells |
miker: For the tree control, one of the comments complains about no accessibility / keyboard control. I know that's a tough requirement for this type of widget, but from what I tried it looks true, so I thought I'd mention it. |
17:13 |
miker |
dbwells: thanks for looking! yeah, it's going to be tough to find something accessible, I think |
17:13 |
miker |
I'm not sure if that's a showstopper for an advanced, staff-only interface or not |
17:18 |
dbs |
jwoodard: the Sitka docs are pretty darned thorough on acquisitions. haven't looked at much else that they have though, I mostly focus on docs.evergreen-ils.org |
17:20 |
miker |
there's angular-nestedsortable that's a big ol' dead end... |
17:26 |
dbwells |
miker: At face value, ngToast seems compact, simple, and targetted, so I'd support running with it. Can't go too wrong there, I think. |
17:29 |
* dbwells |
admits he doesn't have a good view of the big picture |
17:30 |
miker |
there's also this, but it munges the tree to maintain state, and I don't see a way to "select" an item: https://jimliu.github.io/angular-ui-tree/ |
17:33 |
* miker |
runs away |
17:33 |
dbwells |
yeah, I looked over that one quickly as well. My first impression of the other one was more positive. |
17:43 |
|
mrpeters joined #evergreen |
17:44 |
|
bmills joined #evergreen |
17:44 |
|
mrpeters left #evergreen |
20:57 |
|
bmills joined #evergreen |
23:46 |
|
bmills joined #evergreen |