Time |
Nick |
Message |
02:09 |
|
_bott_ joined #evergreen |
06:11 |
|
wsmoak joined #evergreen |
06:36 |
|
phasefx joined #evergreen |
07:01 |
|
dreuther joined #evergreen |
07:44 |
|
rjackson-isl joined #evergreen |
08:23 |
|
akilsdonk joined #evergreen |
08:31 |
|
Shae joined #evergreen |
08:33 |
|
mrpeters joined #evergreen |
08:42 |
|
mmorgan joined #evergreen |
08:57 |
|
Dyrcona joined #evergreen |
09:07 |
|
kmlussier joined #evergreen |
09:17 |
kmlussier |
The last time we had an informal discussion about bug 1074096 in IRC, am I remembering correctly that we had reached a small consensus that we could remove the bib call number search since most sites don't really use bib call numbers? |
09:17 |
pinesol_green |
Launchpad bug 1074096 in Evergreen "Advanced Search by Bib Call Number Returns 0 Results" (affected: 2, heat: 12) [Undecided,Triaged] https://launchpad.net/bugs/1074096 |
09:22 |
|
maryj joined #evergreen |
09:35 |
jeff |
kmlussier: "remove" by disabling but leaving a template config option or similar to re-enable? |
09:37 |
kmlussier |
I don't recall if defined what removed meant. But if we leave a config option, then we should probably look into fixing the search. |
09:37 |
jeff |
i like defaults that reflect how most people configure Evergreen, though I worry about features that are hidden-for-most... rotting, for lack of better term. |
09:37 |
* kmlussier |
is trying to find the logs with the discussion. |
09:37 |
jeff |
ah, i didn't look at the bug today to refresh my memory on what was actually broken or not. |
09:38 |
jeff |
i had the (perhaps mistaken) impression that it was more of an expectation issue -- that there were zero results for good reasons, but it was confusing/non-helpful |
09:39 |
kmlussier |
jeff: I'm not quite sure actually. I thought it was broken, but, since we don't use it, I admit I haven't paid close attention when the topic is raised. |
09:40 |
tsbere |
I thought it worked fine....the wording just confuses people who think they are searching item call numbers and not "in the marc record recommended" call numbers |
09:41 |
kmlussier |
Ah, I found it. |
09:41 |
kmlussier |
What call number field would that be? |
09:42 |
kmlussier |
http://irc.evergreen-ils.org/evergreen/2014-10-09#i_130269 |
09:42 |
tsbere |
I think it is supposed to be something like the 050? |
09:42 |
tsbere |
or was it 060....maybe both? |
09:42 |
* tsbere |
isn't sure anymore |
09:43 |
tsbere |
Oh, huh....if that is identifier|bibcn then it is the 099 |
09:44 |
jeff |
in stock master, it's 099 -- yeah |
09:46 |
kmlussier |
So the bug report says that it used to work for call numbers in 082, 050 or 092. |
09:46 |
jeff |
which is actually different from the logic used to populate some "Bib Call" fields in the staff client. |
09:47 |
kmlussier |
I'm guessing that if somebody wanted to use a different field, they would just need to change the definition for identifier|bibcn |
09:49 |
jeff |
open-ils.cat.biblio.record.marc_cn.retrieve keys off of the call number class to flip between 080ab,082ab,092abef for dewey, 050ab,055ab,090abef for LC, or 050ab,055ab,060ab,070ab,080ab,082ab,086ab,088ab,090,092,096,098,099 for generic. if no class is provided, it falls back to a default that currently is the same as the generic list. |
09:52 |
eeevil |
the "bib call" fields for guessing the best callnumber label are orthogonal, if similarly named. making the two line up could improve usability of the search field, but a config change to the one used in call number creation would require a reingest for the search field to line up |
09:53 |
eeevil |
(just to add a little context, if it wasn't obvious) |
09:54 |
jeff |
thanks. i had it that way, but it helps to be explicit, especially since we know we come back to the logs from time to time. :-) |
09:55 |
kmlussier |
Yup! I added links to this log and the previous log to the bug report just so we don't lose the discussion. |
09:55 |
eeevil |
specifically, making the search field line up with the generic one (assuming no local changes) should cover everything since it's a superset of dewey, lc and "local by convention" |
09:55 |
kmlussier |
Now I'll move on to working on something that our libraries actually use. :) |
09:56 |
eeevil |
or, we could just remove the search field :) ... I was proven wrong in the last discussion re PINES use of that, IIRC |
09:56 |
kmlussier |
eeevil: Yes, that's right. csharp said they weren't using it anymore. |
10:04 |
phasefx |
but academic libraries want it? |
10:05 |
kmlussier |
phasefx: I imagine it's more of a single library issue rather than an academic library issue. |
10:05 |
kmlussier |
We have academics, but they are all in consortia where libraries use different call numbers. A bib call number doesn't make much sense in that context. |
10:05 |
* phasefx |
nods |
10:06 |
phasefx |
I don't really grok how a bib call number makes sense in any context :) |
10:06 |
kmlussier |
Yes, I was just thinking the same thing. |
10:07 |
phasefx |
it's like having a bib spine label |
10:07 |
eeevil |
I think it's probably useful in a "single policy" constorium, but, those seem more rare than I'd imagine ;) |
10:08 |
kmlussier |
It could be that it provides a way to get a list of search results by call number that doesn't bring you to the shelf browse. But I would prefer to see that need addressed by doing a new search based on volume/call number with results that display similar to the bib call number search. |
10:08 |
kmlussier |
eeevil: But couldn't the volume/call number be just as useful in a "single policy" consortium or single library? |
10:09 |
eeevil |
kmlussier: absolutely |
10:09 |
kmlussier |
"single policy" consortium sounds like an oxymoron to me. ;0 |
10:09 |
eeevil |
heh. POINTS |
10:09 |
kmlussier |
Bleh. Now I'm doing typos with my emoticons. |
10:16 |
|
kmlussier1 joined #evergreen |
10:33 |
|
kmlussier joined #evergreen |
11:12 |
|
mmorgan1 joined #evergreen |
11:13 |
|
jwoodard joined #evergreen |
11:13 |
jeff |
heh. i'm remembering a presentation from one organization that had lots of individual policies within their evergreen shared system where someone from a larger single[ish]-policy consortium spoke up |
11:13 |
jeff |
i can't remember if that was in the context of "please don't tell our individual libraries, then they'll want it" or what :-) |
11:18 |
dbwells |
kmlussier: Just to add another data point, we've disabled the bib call number search here. And we are both a single library and an academic :) It's just too much trouble all around to maintain for the value it might bring. |
11:19 |
|
sarabee joined #evergreen |
11:22 |
kmlussier |
dbwells++ Thanks! |
11:33 |
|
collum joined #evergreen |
11:34 |
* berick |
wonders why we explicitly mention automake/autoconf/libtool in the EG install docs when they are already installed during the opensrf install |
11:34 |
|
remingtron joined #evergreen |
11:34 |
berick |
i might remove those for bug #1392759 |
11:34 |
pinesol_green |
Launchpad bug 1392759 in Evergreen "Developer/Packager Makefile.install targets" (affected: 1, heat: 6) [Wishlist,New] https://launchpad.net/bugs/1392759 |
11:47 |
|
Dyrcona joined #evergreen |
11:48 |
|
sandbergja joined #evergreen |
11:57 |
|
Shae_ joined #evergreen |
11:59 |
|
Dyrcona joined #evergreen |
12:11 |
remingtron |
kmlussier: do you want to help organize events of the docs day tmrw? I'm thinking of the Google hangout, not sure what else is needed |
12:12 |
kmlussier |
remingtron: Sure! |
12:12 |
kmlussier |
Has anyone assigned themselves to any tasks? |
12:12 |
remingtron |
kmlussier++ |
12:12 |
remingtron |
not sure |
12:13 |
kmlussier |
Well, I have. But I don't see anyone else. |
12:14 |
|
mllewellyn joined #evergreen |
12:14 |
kmlussier |
Well, we have a DIG meeting today and can hopefully recruit some people there. |
12:20 |
|
sandbergja joined #evergreen |
12:20 |
|
jihpringle joined #evergreen |
12:21 |
|
mtcarlson joined #evergreen |
12:53 |
|
nhilton joined #evergreen |
13:23 |
remingtron |
kmlussier: yes, recruiting at the DIG meeting, good idea |
13:28 |
|
mmorgan1 left #evergreen |
13:28 |
|
mmorgan1 joined #evergreen |
13:30 |
|
mmorgan1 left #evergreen |
13:30 |
|
mmorgan joined #evergreen |
13:35 |
|
yboston joined #evergreen |
13:38 |
kmlussier |
@quote random |
13:38 |
pinesol_green |
kmlussier: Quote #95: "< jeff> i feel a great disturbance in the code... as if $NUMBER of Dumper() calls cried out, and were removed." (added by csharp at 11:40 AM, October 29, 2014) |
13:40 |
jeff |
heh |
13:49 |
|
nhilton_ joined #evergreen |
13:54 |
remingtron |
yboston: DIG meeting today at 2pm, right? |
13:54 |
yboston |
yes, I was just about to post that the DIG meeting |
13:54 |
yboston |
starts at 2 PM EST |
13:54 |
yboston |
( a few minutes from now) |
13:55 |
remingtron |
ah, sorry to steal your thunder |
13:56 |
yboston |
no worries, I was not at the office this morning and I did not get a chance to send out a remidneremail |
14:00 |
yboston |
#startmeeting 2014-12-04 - DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting |
14:00 |
pinesol_green |
Meeting started Thu Dec 4 14:00:37 2014 US/Eastern. The chair is yboston. Information about MeetBot at http://wiki.debian.org/MeetBot. |
14:00 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
14:00 |
pinesol_green |
The meeting name has been set to '2014_12_04___dig_monthly_meeting_evergreen_documentation_interest_group__dig__monthly_meeting' |
14:00 |
yboston |
The agenda can be found here http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_meeting_20141204-agenda |
14:01 |
yboston |
#topic Introductions |
14:01 |
yboston |
Please feel free to start introducing yourselves... |
14:01 |
yboston |
#info yboston is Yamil Suarez @ Berklee College of Music - DIG meeting facilitator |
14:01 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
14:01 |
remingtron |
#info remingtron is Remington Steed, Hekman Library (Calvin College) |
14:03 |
remingtron |
quiet day in #evergreen |
14:03 |
|
purcellm joined #evergreen |
14:03 |
yboston |
I always set a timer to decide when I start the meeting. Almost done |
14:04 |
remingtron |
well, everyone with Action Items is here, I guess that's something |
14:04 |
kmlussier |
It's a busy time of year. Sometimes hard to get people to a meeting. |
14:04 |
yboston |
good point. I am ready to start |
14:05 |
remingtron |
kmlussier: true, holidays and all |
14:05 |
yboston |
it is about quality not quantity |
14:05 |
yboston |
:) |
14:05 |
purcellm |
#info purcellm is michelle purcell drexel |
14:05 |
remingtron |
I should have brought cookies |
14:05 |
kmlussier |
Ha ha. But quantity does help. :) |
14:05 |
yboston |
I know :( |
14:05 |
kmlussier |
Welcome purcellm! |
14:05 |
remingtron |
welcome purcellm! |
14:05 |
|
mtcarlson joined #evergreen |
14:05 |
purcellm |
Hi! |
14:05 |
yboston |
purcellm++ |
14:05 |
|
nhilton joined #evergreen |
14:05 |
yboston |
I think we can start now |
14:06 |
remingtron |
yboston: go for it |
14:06 |
yboston |
#topic past meeting action items |
14:06 |
sandbergja |
#info sandbergja is Jane Sandberg, Linn-Benton Community College |
14:06 |
kmlussier |
Hi sandbergja! |
14:06 |
yboston |
#topic yboston will contact krvmga to check in on his 2.7 docs work |
14:06 |
remingtron |
welcome sandbergja! |
14:07 |
yboston |
I reached out to him last week (or earlier) |
14:07 |
yboston |
he said he still needed more work to be done on these docs |
14:08 |
yboston |
he said he would try to get it donw and contact us |
14:08 |
yboston |
I can reach out to him again? |
14:08 |
remingtron |
sound like he was wanting/willing for help? |
14:08 |
yboston |
yes, he wanted to finish the work |
14:08 |
remingtron |
you mean, finish it himself? or give it to someone else? |
14:09 |
yboston |
yes, himself |
14:09 |
remingtron |
ah, okay |
14:09 |
yboston |
just looked up our conversation. he still needs to test |
14:09 |
yboston |
that EG behaves as his docs describes |
14:09 |
yboston |
tis was back on November 26 |
14:09 |
remingtron |
I'd say yes, just follow up with him again, whenever seems best |
14:10 |
yboston |
OK |
14:10 |
yboston |
#action yboston will contact krvmga to check in on his 2.7 docs work |
14:10 |
yboston |
#topic kmlussier will complete the marc stream importer work and check on the status of the RDA docs. |
14:10 |
* kmlussier |
needs to defer her action items. |
14:11 |
yboston |
no worries |
14:11 |
kmlussier |
Sorry! The month goes by more quickly than I expect. |
14:11 |
remingtron |
kmlussier: any way we can help? |
14:11 |
kmlussier |
RDA should be easy. I just need to do it. |
14:11 |
yboston |
#action kmlussier will complete the marc stream importer work and check on the status of the RDA docs. |
14:11 |
kmlussier |
I'm basing the marc stream importer documentation on notes I received from somebody else. |
14:12 |
yboston |
I don't mind restarting the action item |
14:12 |
kmlussier |
I can dig those up and post them on a google doc somewhere if somebody wants to help with it. |
14:12 |
sandbergja |
I can help with that, if you want to go the google doc route |
14:12 |
kmlussier |
It's not just documentation for the new feature. I don't think there's every been marc stream importer documentation, so it's really starting from scratch. |
14:13 |
yboston |
kmlussier: should I add an action item for sharing what you have? |
14:13 |
kmlussier |
sandbergja: OK. Can you send me a private message with the e-mail address you have linked to your Google account? |
14:13 |
remingtron |
sandbergja++ #for sharing the load |
14:13 |
yboston |
sandbergja++ |
14:13 |
kmlussier |
I probably won't pull it together until next week since I really want to focus on the web client tomorrow. |
14:13 |
sandbergja |
sounds good! |
14:13 |
kmlussier |
sandbergja++ indeed! |
14:14 |
yboston |
if we want to move on, this is the perfect segway to the web client work |
14:14 |
remingtron |
yboston: go right ahead |
14:14 |
yboston |
#topic Web Client documentation work |
14:15 |
yboston |
thanks to remingtron for putting together the poll and other logistics |
14:15 |
yboston |
remingtron++ |
14:15 |
yboston |
#link http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:webclient |
14:15 |
kmlussier |
remingtron++ |
14:15 |
sandbergja |
remingtron++ |
14:15 |
remingtron |
you're welcome. I'm not sure what comes next, though. |
14:16 |
kmlussier |
I think we need more people to sign up for tasks. I tried to flesh out the outline for what can be documented tomorrow. Maybe we need to send out one last reminder asking people to assign themselves? |
14:16 |
yboston |
of the top of my head, when was the test server built? I wonder what commits it contains, in case new features are in master that are not in the test server? |
14:16 |
kmlussier |
Actually, the opposite is true |
14:16 |
yboston |
I still need to assign myself a tasks |
14:17 |
kmlussier |
webby has bug fixes that have not been merged into master yet. |
14:17 |
yboston |
good to know |
14:17 |
remingtron |
#link https://webby.evergreencatalog.com/eg/staff/ |
14:17 |
kmlussier |
graced also told us she would try to make sure webby stays as stable as possible tomorrow. |
14:17 |
yboston |
by the way, applying 2020 hindsight |
14:17 |
kmlussier |
graced++ |
14:17 |
remingtron |
graced++ |
14:17 |
yboston |
I would have mentioned in our emails that no software instalation was needed to help out |
14:18 |
yboston |
I wonder if folks assumed they needed to install software for documenting, but then again it is a web client |
14:19 |
remingtron |
yboston: good question. I'll send another reminder today, with the added note about no software needed |
14:19 |
kmlussier |
And we want a Google Hangout tomorrow, right? |
14:19 |
yboston |
BTW, should one of us host a google hangout? I can do that |
14:19 |
yboston |
you read my mind |
14:20 |
remingtron |
yes, I'd be glad for one of you to host it |
14:20 |
kmlussier |
remingtron and I were talking about it earlier. I'm happy to set it up too. |
14:20 |
kmlussier |
heads says yboston sets it up; tails is me. |
14:20 |
kmlussier |
@coin |
14:20 |
pinesol_green |
kmlussier: tails |
14:21 |
remingtron |
kmlussier: good decision making tool |
14:21 |
kmlussier |
remingtron: I need to use it more often. :) |
14:21 |
yboston |
if you have any issues let me know, and I can step in |
14:21 |
remingtron |
starting about 8am EST? |
14:21 |
yboston |
should we mention that you ned to share your Google accoutn email address to Kathy in an email tomorrow? |
14:22 |
remingtron |
kmlussier: yeah, do you want to send the info to the DIG list about joining? |
14:22 |
kmlussier |
Yes, I can do that. |
14:22 |
remingtron |
kmlussier++ |
14:22 |
kmlussier |
I'll also post a link in here tomorrow. |
14:23 |
kmlussier |
And I'll have it ready by 8 a.m. I don't have to commute tomorrow, so I should be able to start early. |
14:23 |
yboston |
cool |
14:24 |
yboston |
BTW, off the top of my head I don't know what feature of the web cleints to docuemnt. I am open to suggestions or if someone want to team up with me to geta feel of how to make docs |
14:24 |
yboston |
remeber that AsciiDoc is not required |
14:25 |
yboston |
Also, remind me where we are placing the new docs we create? an appendix section? |
14:25 |
|
DPearl joined #evergreen |
14:25 |
remingtron |
yboston: good question! |
14:26 |
kmlussier |
I think we talked about having a separate section. |
14:26 |
purcellm |
I need to head to another meeting. I'll take a look at the web client and try and find a task to assign myself to. |
14:26 |
yboston |
thanks purcellm |
14:26 |
purcellm |
Bye. |
14:26 |
kmlussier |
purcellm++ |
14:26 |
* kmlussier |
looks for old meeting minutes |
14:27 |
remingtron |
I don't think we ever discussed where in the docs to put this stuff |
14:27 |
remingtron |
I think appendix sounds fine for now |
14:28 |
remingtron |
maybe with links from the current staff client docs in some places |
14:28 |
kmlussier |
We discussed it in October. The consensus was a separate section at the time. http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-10-02-14.00.log.html |
14:29 |
kmlussier |
Around the 14:31 point of the meeting. |
14:29 |
remingtron |
thanks kmlussier |
14:29 |
kmlussier |
And then it looks like we need to backport it to 2.7 |
14:30 |
yboston |
I should have made an action item to bring this topic up to the list |
14:30 |
kmlussier |
I don't think you did because we had general consensus at the meeting. |
14:30 |
yboston |
but the early consensus was a new section |
14:30 |
kmlussier |
I can create the section when this meeting is done to get ready for tomorrow if it helps. |
14:30 |
yboston |
OK |
14:31 |
remingtron |
great |
14:31 |
yboston |
anything else to talk about tomorrow? |
14:31 |
remingtron |
yes briefly |
14:32 |
yboston |
go ahead |
14:32 |
yboston |
I did not mean to rush you |
14:32 |
remingtron |
all are welcome to improve the wiki page with helpful instructions for participants |
14:32 |
remingtron |
(no worries) |
14:33 |
|
akilsdonk joined #evergreen |
14:33 |
remingtron |
I added some brief "How to Help" steps |
14:33 |
remingtron |
and basic info about the demo server |
14:34 |
yboston |
very nice |
14:34 |
remingtron |
thanks |
14:35 |
yboston |
after the meeting I will put my name down in a couple of sections. |
14:35 |
yboston |
does it matter if they are based on XUL code, like the patron record itnerface? |
14:36 |
yboston |
I guess I can docuemnt the new look with new screenshots |
14:36 |
kmlussier |
yboston: Yeah, that documentation probably doesn't need much updating. But you might want to do the new screenshots if it looks a little different. |
14:36 |
remingtron |
yboston: yes, I think the goal is to work from the new interface. In most case it is very similar to the XUL, but not always |
14:37 |
kmlussier |
I think we may have new scrollbars that we didn't see in the patron editor before. |
14:37 |
kmlussier |
remingtron: In the case of patron registration, they just ported over the Dojo interface. |
14:37 |
remingtron |
ah, got it |
14:37 |
kmlussier |
yboston: That's the one you were asking about, right? |
14:38 |
yboston |
I am not 100% sure of what the section called "III. Circulation - Patron Record" covers |
14:38 |
yboston |
I suspect it might mean editign a patron record at the very least |
14:38 |
kmlussier |
yboston: Those section titles were just copied over from the existing docs. |
14:39 |
yboston |
I just signed myself for it |
14:39 |
yboston |
OK |
14:39 |
kmlussier |
yboston: So it would be anything listed here - http://docs.evergreen-ils.org/dev/_circulation_patron_record.html |
14:40 |
kmlussier |
Which is a lot. You might want to divvy it up further. |
14:40 |
remingtron |
I think our goal for tomorrow should be to do what the web client has done: basically copy the existing documentation and make the minimum changes to work with the web client |
14:40 |
remingtron |
(meaning, the web client is mostly a copy of the XUL client) |
14:40 |
kmlussier |
Yes, I was planning to copy files from the existing docs and edit them accordingly. |
14:40 |
remingtron |
so if we find big problems or holes in the docs, let's make notes about it but not get side tracked |
14:41 |
yboston |
OK |
14:41 |
remingtron |
since I tend to get side tracked by things :) |
14:41 |
kmlussier |
remingtron: Yes, me too! A small doc change often turns into a day-long revamp of a section. :) |
14:42 |
yboston |
yep |
14:42 |
remingtron |
kmlussier: so, so familiar |
14:42 |
remingtron |
alright, anything else about tomorrow? |
14:43 |
kmlussier |
Nothing from me. |
14:43 |
yboston |
I think I am all set |
14:43 |
remingtron |
great, back to you, maestro yboston |
14:43 |
yboston |
I had to small points to bring up before the meeting ends |
14:43 |
yboston |
(gracias) |
14:43 |
yboston |
#topic yboston will follow up with gmcharlt and Robert about provisioning a VM for DIG |
14:44 |
yboston |
I forgot abotu this action item until like an hour ago, so I send out an email to the involved parties and will await a reponse |
14:44 |
yboston |
#action yboston will follow up with gmcharlt and Robert about provisioning a VM for DIG |
14:44 |
remingtron |
yboston++ #meetings encourage us to do things :) |
14:44 |
yboston |
#topic Date for DIG monthly meeting in January |
14:45 |
yboston |
If we follow that usual schedule, the next meeting would be on Janaury 1st |
14:45 |
yboston |
I suspect, that we don't want to do that |
14:45 |
remingtron |
hm, following week then? |
14:46 |
yboston |
yes, and until now I thought I was unavailable but I will be at work |
14:46 |
yboston |
oh wait, there is an Evergreen for academics meeting that day |
14:46 |
yboston |
at 2 PM |
14:47 |
yboston |
I can send out a an email tot he DIG list to see if we can meet before or after that meeting |
14:47 |
remingtron |
sure, or how about the 15th? |
14:47 |
remingtron |
you can ask the list or do a doodle |
14:47 |
yboston |
EG board meeting at 2 PM :) |
14:47 |
remingtron |
thursdays are packed! |
14:48 |
yboston |
I can put out a doodle poll |
14:48 |
kmlussier |
+1 to doodle |
14:48 |
yboston |
I suspect I might want to wait until early Janaury to send it out |
14:48 |
remingtron |
sounds fine |
14:49 |
yboston |
OK |
14:49 |
yboston |
I think we can wrap things up, unless someone has any comments or question, specially from newer members or lurkers |
14:49 |
remingtron |
you can repeat my other action item for next meeting |
14:50 |
yboston |
#action remingtron will set up doodle to set up a meeting on IRC in Janaury 2015 to discuss re-organizing the EG docs |
14:50 |
remingtron |
thanks |
14:50 |
yboston |
I totally misread that action item as being about the web client |
14:51 |
yboston |
anything else? |
14:51 |
remingtron |
nope |
14:51 |
yboston |
OK will end the meeting, thanks |
14:51 |
remingtron |
thanks for leading, as always! |
14:51 |
yboston |
#endmeeting |
14:51 |
pinesol_green |
Meeting ended Thu Dec 4 14:51:47 2014 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
14:51 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-12-04-14.00.html |
14:51 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-12-04-14.00.txt |
14:51 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-12-04-14.00.log.html |
14:51 |
remingtron |
yboston++ |
14:52 |
kmlussier |
yboston++ |
14:52 |
sandbergja |
yboston++ |
14:52 |
|
sbrylander joined #evergreen |
14:58 |
DPearl |
Hi. I need some help. I'm trying to add an api in Cat.pm. I have added the entry to constants.js, written the sub in Cat.pm, registered the method... I am getting a "Method [open-ils.cat.asset.move_attached_parts] not found for OpenILS::Application::Cat","status":404}" error, which leads me to think simple_request is failing early due to %api not having the entry. Where/how is api defined? |
15:02 |
phasefx |
DPearl: I would try the call in srfsh first, or in srfsh, introspect open-ils.cat and see if it's there |
15:03 |
phasefx |
api does come from constants.js, but that file does exist client side and server side |
15:04 |
phasefx |
I think your constants.js is working correctly based on the error |
15:05 |
phasefx |
the client side doesn't know identifiers like OpenILS::Application::Cat, so your error is coming from the server |
15:06 |
eeevil |
DPearl: have a git commit up somewhere, or paste relevant server code? |
15:07 |
DPearl |
eeevil: No commit yet.. I'll paste code. |
15:14 |
pastebot |
"DPearl" at 64.57.241.14 pasted "Code for new API" (69 lines) at http://paste.evergreen-ils.org/16 |
15:15 |
DPearl |
I'll also paste error message |
15:16 |
pastebot |
"DPearl" at 64.57.241.14 pasted "Error message" (7 lines) at http://paste.evergreen-ils.org/17 |
15:16 |
tsbere |
DPearl: Could it be that your Cat.pm isn't actually being loaded? Especially if you have installed from packages and source or something like that... |
15:18 |
DPearl |
tsbere: It is possible, I suppose. I think an earlier version elicited a syntax error, but that's a decent thought. |
15:19 |
DPearl |
eeevil: phasefx: In additon to the pasted code, there is a database function to actually do the dirty work. |
15:22 |
eeevil |
DPearl: 1) what tsbere said ... 2) as an aside, you probably want to check a permission for that. otherwise, any logged-in patron could move parts around |
15:23 |
kmlussier |
That could be fun! |
15:24 |
DPearl |
phasefx: The introspect (handy function, that) revealed no knowledge of the api. How do I address this? Just a restart of Evergreen? |
15:24 |
eeevil |
and a question: is this meant to be used when merging records, or moving copies between call numbers, or something else? or all of those? |
15:24 |
phasefx |
DPearl: or just a restart of open-ils.cat |
15:24 |
eeevil |
DPearl: yeah. you have to restart the service, at least |
15:25 |
eeevil |
in modern opensrf: osrf_control --service open-ils.cat --restart # iirc |
15:25 |
DPearl |
eeevil: Agreed. I will find the appropriate perm to put in. This is meant to be used when moving copies form one call number to another. I believe the merging records issue has already been addressed. |
15:25 |
eeevil |
and maybe a --localhost |
15:25 |
kmlussier |
bug 904472 |
15:25 |
pinesol_green |
Launchpad bug 904472 in Evergreen "Transferring items with monographic parts to a new bib record causes problems with holds placement" (affected: 4, heat: 34) [Undecided,Triaged] https://launchpad.net/bugs/904472 - Assigned to Dan Pearl (dpearl) |
15:25 |
DPearl |
eeevil: Thanks. It might actually work if I restart the appropriate services. |
15:26 |
DPearl |
eeevil++ |
15:26 |
eeevil |
:) |
15:26 |
DPearl |
phasefx++ |
15:26 |
eeevil |
phasefx++ |
15:31 |
|
mtcarlson joined #evergreen |
15:39 |
|
kbutler joined #evergreen |
15:44 |
kmlussier |
yboston, remingtron: I think I'm changing my mind on what we discussed for incorporating the web client preview in the docs. |
15:44 |
yboston |
OK |
15:45 |
kmlussier |
If we went with the approach I was originally thinking with, with XIII being Web client preview and circ and using the client being sections below it, then those sections would be at a lower level than they are now. I think we want to keep it as consistent with the original documentation as possible. |
15:45 |
kmlussier |
So maybe remingtron's idea to do an appendix is a better one. |
15:47 |
kmlussier |
Hmmm...but I don't know if that approach solves the issue either. |
15:49 |
kmlussier |
Never mind. I take it back. I think we can use the offsets in root.txt to make it behave the way it needs to while the web client is in preview mode. Just ignore my babbling. |
16:01 |
jeff |
offsets++ |
16:02 |
Dyrcona |
(setq c-cont-statement-offset +) |
16:03 |
|
_bott_ joined #evergreen |
16:06 |
mrpeters |
call for testers/sign-offs/improvements -- https://bugs.launchpad.net/evergreen/+bug/1361266 |
16:06 |
pinesol_green |
Launchpad bug 1361266 in Evergreen "Patron self-registration form accepts date of birth in wrong format" (affected: 1, heat: 6) [Undecided,Confirmed] |
16:07 |
mrpeters |
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mrpeters/lp1361266_opac_registration_date_validation |
16:07 |
kmlussier |
mrpeters++ |
16:28 |
|
nhilton_ joined #evergreen |
16:29 |
|
mtcarlson joined #evergreen |
16:37 |
pinesol_green |
[evergreen|Kathy Lussier] Web client section headings - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=feae6dc> |
17:06 |
|
jihpringle joined #evergreen |
17:12 |
|
wsmoak joined #evergreen |
17:12 |
|
wsmoak joined #evergreen |
17:13 |
|
mmorgan left #evergreen |
17:17 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
18:20 |
|
mtj joined #evergreen |
20:21 |
|
nhilton joined #evergreen |
22:47 |
|
mtcarlson joined #evergreen |