| Time |
Nick |
Message |
| 05:14 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 07:20 |
|
Newziky joined #evergreen |
| 07:43 |
|
graced joined #evergreen |
| 07:48 |
|
rjackson_isl joined #evergreen |
| 08:02 |
|
Shae joined #evergreen |
| 08:20 |
|
collum joined #evergreen |
| 08:21 |
|
Shae joined #evergreen |
| 08:25 |
|
ericar joined #evergreen |
| 08:30 |
|
mmorgan joined #evergreen |
| 08:32 |
|
remingtron joined #evergreen |
| 08:33 |
|
akilsdonk joined #evergreen |
| 08:34 |
|
mrpeters joined #evergreen |
| 08:46 |
dbwells |
berick++ # 2.8 |
| 09:09 |
|
maryj joined #evergreen |
| 09:22 |
|
RoganH joined #evergreen |
| 09:34 |
|
yboston joined #evergreen |
| 09:49 |
kmlussier |
gmcharlt++ http://evergreen-ils.org/evergreen-web-team-extends-protocol-support/ |
| 09:54 |
|
ericar_ joined #evergreen |
| 10:02 |
|
jwoodard joined #evergreen |
| 10:03 |
berick |
gmcharlt++ |
| 10:08 |
|
RoganH joined #evergreen |
| 10:11 |
|
Newziky joined #evergreen |
| 10:14 |
|
ThatGuy joined #evergreen |
| 10:15 |
ThatGuy |
Hate to be "that guy" but does anyone know why whenever Evergreen prints to a receipt printer it takes 8ft of receipt paper? |
| 10:16 |
ThatGuy |
Tried reinstalling Evergreen, tried reinstalling the receipt printer and even getting a different one connect to the computer I am currently on. |
| 10:17 |
|
graced joined #evergreen |
| 10:21 |
kmlussier |
ThatGuy: In your workstation printer settings, if you click the Page Setup button, do you have anything entered for margins? |
| 10:22 |
kmlussier |
That is, Page Settings |
| 10:25 |
ThatGuy |
.5 all around |
| 10:28 |
kmlussier |
ThatGuy: Did you have receipt selected when you checked the Page Settings? Also, I would recommend 0 there, but I don't know that .5 would make that much of a difference. |
| 10:28 |
mmorgan |
ThatGuy: Also, try blanking out anything in the Header & Footer section of Page setup. |
| 10:33 |
* kmlussier |
tries to imagine an alternate universe where gmcharlt is a dog person. |
| 10:35 |
ThatGuy |
That seems to have done it. Thank you!! |
| 10:37 |
* kmlussier |
wonders what "that" ended up being. |
| 10:39 |
berick |
kmlussier: "that" was imagining gmcharlt as a dog person |
| 10:39 |
* kmlussier |
chuckles |
| 10:40 |
mmorgan |
"that" makes my head hurt. |
| 10:40 |
mmorgan |
unless of course the dogs are purple ;-) |
| 10:41 |
* bshum |
idly wonders if Darth Tater likes dogs and will strike back later today now. |
| 10:42 |
* gmcharlt |
starts a kickstarter for suits of armor |
| 10:44 |
csharp |
@quote random |
| 10:44 |
pinesol_green |
csharp: Quote #91: "< eeevil> one tiny chunk of code for a man, one giant step toward unified APIs for mankind" (added by csharp at 06:04 PM, September 10, 2014) |
| 10:49 |
|
tater-laptop joined #evergreen |
| 10:51 |
|
Darth_Tater joined #evergreen |
| 10:51 |
Darth_Tater |
Banthas. I like banthas. |
| 10:52 |
|
sandbergja joined #evergreen |
| 10:52 |
bshum |
Heh |
| 10:53 |
tsbere |
kmlussier: Removing header/footer, given the average "length" of a page when using roll paper on most receipt printers not having the footer would allow the automatic "don't print several feet of blank paper" function of the driver to kick in. |
| 10:53 |
* tsbere |
just came back from a meeting >_> |
| 10:59 |
jonadab |
I was not aware receipt printers _had_ a concept of "page". |
| 11:00 |
jonadab |
TIL. |
| 11:08 |
|
ericar_ joined #evergreen |
| 11:10 |
csharp |
yeah, the receipt printer needs to know it's roll paper both at the windows (or OS of choice) level *and* at the Evergreen level |
| 11:12 |
jonadab |
Oh, for the days of DOS, when you could just chuck ASCII text in the general direction of LPT1 and it would Just Work. |
| 11:12 |
* jonadab |
is not entirely serious. But partly. |
| 11:12 |
jeff |
then Windows, where apps doing that approach often resulted in one windows print job per line. |
| 11:12 |
jonadab |
Heh. |
| 11:13 |
jeff |
...and AV software would sometimes eat or cause the lines to be re-ordered, especially on slower hardware... |
| 11:13 |
jonadab |
Now *that* is a complication I never experienced. |
| 11:14 |
|
bmills joined #evergreen |
| 11:16 |
jcamins |
jeff: I spent too much time in libraries. "AV" stands for "Audio/Visual" in my mind. |
| 11:16 |
tsbere |
I never had the "print job per line" issue unless there was not, in fact, a printer on LPT1. |
| 11:17 |
jeff |
tsbere: yes, this would have been with DOS and Windows apps and physical printers on LPT1 |
| 11:17 |
tsbere |
"print job per page" though came up several times.....which was fine until you were dealing with a network printer of some kind and things got mixed together. |
| 11:17 |
jeff |
i suspect it was at least partially to do with the apps (probably) internally writing each line to the LPT1 device. |
| 11:18 |
jonadab |
Yes, likely. |
| 11:18 |
jonadab |
Which isn't what they were really _supposed_ to do under DOS, but it _did_ work... |
| 11:18 |
tsbere |
jeff: If they open LPT1, write a single line, and then close LPT1 I could see "one job per line" - I only ever saw "open LPT1, write out a whole page, close LPT1" in practice, but different programs.... |
| 11:18 |
jonadab |
tsbere: Yes, that's how apps were _supposed_ to do it. |
| 11:18 |
jonadab |
But, you know. |
| 11:19 |
tsbere |
jonadab: I personally viewed the best bet as "open LPT1, write your *entire print job*, close LPT1" |
| 11:20 |
tsbere |
"Each page is a print job" creates issues with shared printers. Though I suppose not as many issues as "each *line* is a print job" >_> |
| 11:20 |
jonadab |
tsbere: Yes, right. I was thinking sub-page-length print jobs, but yeah. |
| 11:21 |
jonadab |
ASCII defines a form feed character for a reason. |
| 11:21 |
tsbere |
actually, I can recall one program that wrote one character at a time to LPT1.....but I don't believe it closed LPT1 each time, so it wasn't as big a deal. Just weird. |
| 11:22 |
jonadab |
That sounds like something an assembly-language program would do as an optimization. |
| 11:22 |
jonadab |
"We think our hand-rolled loop is faster than the string-copying interrupt." |
| 11:23 |
jonadab |
"And being 6% faster is way more important than doing things in a standard way that will be maintainable in the future." |
| 11:24 |
tsbere |
I think it was actually more for "If we run into certain control characters we check to see if we are configured to do special things instead of them" than anything else. |
| 11:24 |
jonadab |
Ah. |
| 11:24 |
tsbere |
Not really sure anymore. Haven't worked with that kind of thing in years. |
| 11:28 |
|
mmorgan joined #evergreen |
| 11:29 |
jcamins |
tsbere: and it sounds like your life is better for it. |
| 11:31 |
tsbere |
jcamins: I dunno. My last foray involved getting what I think was 8bit cash register software to run in a networked windows XP and 2003 server environment. >_> |
| 11:32 |
jeff |
Hrm. Any danger with adding custom entries in action.hold_request_cancel_cause? Doesn't look like there's a sequence, so I suppose local causes starting at id 101 or 1001 would be a good idea... |
| 11:32 |
tsbere |
Hmmm....or was the hospital patient software after that.....same idea, though |
| 11:32 |
tsbere |
jeff: I don't think there is a danger (they would show up in the staff client interface) but bumping the default ID up a bit for people doing so wouldn't hurt, IMO |
| 11:33 |
tsbere |
jcamins: Either way, in both cases of "get ancient software to run on newer hardware" I actually ended up installing an emulator intended for DOS games. To get cash registers and hospital patient systems working. :D |
| 11:38 |
|
mllewellyn joined #evergreen |
| 11:38 |
jeff |
hrm. in a future release, we should probably have an option for hold cancel causes that are not selectable by staff. |
| 11:50 |
mmorgan |
jeff++ |
| 11:51 |
|
akilsdonk joined #evergreen |
| 11:56 |
jeff |
system-only, and all that |
| 12:26 |
|
darshana joined #evergreen |
| 12:27 |
* dbs |
dives back into the waters of trying to figure out why holds aren't being captured opportunistically one day, but will get captured the next day. |
| 12:27 |
dbs |
Time to see if someone's been playing around with YAOUS like hold stalling |
| 12:28 |
tsbere |
jeff: "Patron via OPAC" being a good one for that. ;) |
| 12:29 |
tsbere |
dbs: Half the time we get that I find out that the copy either didn't exist the previous day or was marked as not holdable the previous day. In both cases the copy isn't in the hold copy map table at opportunistic capture time. |
| 12:30 |
tsbere |
(doesn't help if you are dealing with "this brand new hold won't capture this copy..." issues, mind you, but we don't get many of those questions anymore) |
| 12:30 |
dbs |
tsbere: Yeah, the "marked as not holdable" has come up a number of times. |
| 12:31 |
* dbs |
curses copy attribute templates that mark items as "not holdable" for belt & suspenders because they never get unset |
| 12:31 |
dbs |
Also we're in the netherland of still using script-based circ so there's plenty of sharp edges now |
| 12:32 |
tsbere |
Ahhh. But "not in the hold copy map table" still trumps all hold rules. Because the rules aren't checked if the copy isn't in the table for the hold. |
| 12:37 |
mmorgan |
We initially had confusion with items in non-holdable statuses not capturing. |
| 12:37 |
mmorgan |
An item in a nonholdable status is checked in, it doesn't capture, even with retargeting modifiers on. |
| 12:37 |
mmorgan |
A second checkin with retargeting modifiers on will capture it. |
| 12:38 |
mmorgan |
We changed the holdability flag of a number of statuses because of this. |
| 12:42 |
tsbere |
mmorgan: That can be a problem, yea. "This is going to go holdable after checkin" can create headaches. |
| 12:49 |
jeff |
dbs: QA reports that flag copies with holdable/circulate/visible false can help. :-) |
| 12:50 |
jeff |
dbs: i.e., "don't use these, use the shelving location level attributes (and/or circ mod for holdable) instead", and treat their being set as an error to correct :-) |
| 12:57 |
gmcharlt |
web team meeting in five minutes |
| 13:01 |
gmcharlt |
#startmeeting Evergreen Web Team meeting 1 April 2015 |
| 13:01 |
pinesol_green |
Meeting started Wed Apr 1 13:01:55 2015 US/Eastern. The chair is gmcharlt. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 13:01 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
| 13:01 |
pinesol_green |
The meeting name has been set to 'evergreen_web_team_meeting_1_april_2015' |
| 13:02 |
gmcharlt |
#info Agenda at http://wiki.evergreen-ils.org/doku.php?id=webteam:meetings:agenda:2015-04-01 |
| 13:02 |
gmcharlt |
#topic Introductions |
| 13:02 |
gmcharlt |
introduce yourself with #info |
| 13:02 |
bshum |
#info bshum = Ben Shum, Bibliomation |
| 13:02 |
gmcharlt |
#info gmcharlt = Galen Charlton, ESI |
| 13:02 |
bshum |
I apologize in advance, cause I'll have to skip out around 1:30 for another conflicting meeting :\ |
| 13:03 |
RoganH |
#info RoganH = Rogan Hamby, Grue Hunter With One Torch Left |
| 13:03 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 13:03 |
gmcharlt |
RoganH++ |
| 13:03 |
gmcharlt |
(everybody, breathe shallowly!) |
| 13:04 |
RoganH |
gmcharlt++ |
| 13:04 |
gmcharlt |
#topic Announcements |
| 13:04 |
gmcharlt |
#info Evergreen now has a site in the gophersphere: http://evergreen-ils.org/evergreen-web-team-extends-protocol-support/ |
| 13:05 |
gmcharlt |
#info visit it at gopher://gopher.evergreen-ils.org/ |
| 13:05 |
kmlussier |
We're on the cutting edge now! |
| 13:05 |
gmcharlt |
#info If anybody with a login to the web server has absolutely nothing better to do with their time, play around in /var/gopher to edit content ;) |
| 13:06 |
gmcharlt |
though seriously, anybody who makes the effort to load up a gopher client and visit will be rewarded with a couple easter eggs from Evergreen's early history |
| 13:06 |
bshum |
it is entertaining :) |
| 13:07 |
gmcharlt |
any other announcements? |
| 13:07 |
bshum |
gmcharlt++ |
| 13:08 |
gmcharlt |
so, moving on |
| 13:08 |
gmcharlt |
#topic Evergreen hashtag |
| 13:08 |
gmcharlt |
kmlussier: bshum: GO! |
| 13:09 |
kmlussier |
bshum and I are using the #evgils hashtag now for our Evergreen-related tweets. |
| 13:09 |
kmlussier |
Because the #egils hashtag is being used for a few different purposes outside of the Evergreen world. |
| 13:10 |
kmlussier |
One of which is beer, which is never a bad thing to see in my Evergreen stream. |
| 13:10 |
kmlussier |
I have also updated Twitterfeed to use both #evgils and #egils for any Planet Evergreen tweets. |
| 13:11 |
kmlussier |
With the intent of eventually moving to just #evgils in the not-too-distant future. |
| 13:11 |
bshum |
I figure if we make this change, we should also do some sort of media thingy on the website telling people what the official hashtag is. And maybe do some stream plugin or something to Wordpress. I imagine that sort of thing exists. |
| 13:11 |
gmcharlt |
what do you mean by stream lugin? |
| 13:11 |
bshum |
"official" with quotes. Since Twitter being Twitter, anyone can tweet whatever they want. |
| 13:11 |
gmcharlt |
*plugin |
| 13:12 |
RoganH |
What would the plugin for Wordpress do? |
| 13:12 |
kmlussier |
Something that displays all #evgils posts maybe? |
| 13:12 |
bshum |
In retrospect, let me do more investigation on how/why/what that might actually entail. |
| 13:12 |
bshum |
It was more of a random thought that hadn't fully manifested in my head yet. |
| 13:13 |
gmcharlt |
there's the potential for minor dragons with putting up a hashtag widget unless it's watched |
| 13:13 |
bshum |
True. |
| 13:14 |
gmcharlt |
FWIW, I don't mind #evgils, and I"m happy to do my bit to ensure that it gets used along with #egils |
| 13:14 |
bshum |
That might be beyond what we need to do then. |
| 13:14 |
gmcharlt |
and if #egils goes away organically, great |
| 13:14 |
RoganH |
There is one use of #egils I worry about. I haven't seen anything too bad from it so I welcome the change. |
| 13:14 |
gmcharlt |
and if somebody wants to make a post on the evgils.org blog ;) advocating for it, well... go for it! |
| 13:15 |
kmlussier |
Looking at my Twitter feed, it looks like bshum, gmcharlt and I are the ones who primarily use the hashtag. |
| 13:15 |
RoganH |
I don't tweet much but I'll make sure I use the new one when I do. |
| 13:15 |
kmlussier |
If bshum and I stop using #egils, it should go away organically soon enough. :) |
| 13:15 |
kmlussier |
I can post something to the blog. |
| 13:15 |
|
jihpringle joined #evergreen |
| 13:16 |
bshum |
kmlussier++ |
| 13:16 |
gmcharlt |
just don't overpolice it please if somebody uses the "wrong" #hashtag |
| 13:16 |
gmcharlt |
hmm, potentially we could use twarc or something to archive the hashtag |
| 13:16 |
RoganH |
Now, you know librarians never get anal about exacting terminology. |
| 13:16 |
kmlussier |
Nope. I have no intention of policing the Internets |
| 13:17 |
gmcharlt |
though that might be a little too Big Brotherish |
| 13:17 |
gmcharlt |
so, fair to say that we've got a consensus to advocate for #evgils and see what ahppens? |
| 13:17 |
kmlussier |
Archiving the hashtag might not be a terrible idea. I often have a need to search out old posts I saw on Twitter. |
| 13:17 |
RoganH |
I wouldn't bother archiving it but I tend to think of twitter as an ephemeral thing. |
| 13:19 |
gmcharlt |
ok, |
| 13:19 |
gmcharlt |
#action We shall march forth under the #evgils banner! |
| 13:19 |
gmcharlt |
#topic Doc testing VM |
| 13:20 |
gmcharlt |
#info This has moved forward a bit - gmcharlt has an IP address courtesy of csharp, access to the main docs server, and now just needs to create the VM |
| 13:21 |
gmcharlt |
#topic Evergreen library directory |
| 13:21 |
gmcharlt |
#info Erica has been making updates to it |
| 13:21 |
bshum |
gmcharlt++ csharp++ |
| 13:21 |
gmcharlt |
ericar++ |
| 13:21 |
bshum |
ericar++ |
| 13:21 |
* bshum |
is just going to give karma to everybody who's awesome today :) |
| 13:21 |
bshum |
... and everyday |
| 13:22 |
gmcharlt |
#topic Trademark page |
| 13:22 |
gmcharlt |
#action gmcharlt will pursue this in April, and request that it be put on the EOB meeting agenda this month if there's anything that can't be handled over me |
| 13:23 |
gmcharlt |
(though I anticipate that email will suffice) |
| 13:23 |
kmlussier |
gmcharlt: I'm happy to help if you need any. |
| 13:23 |
gmcharlt |
kmlussier++ |
| 13:24 |
gmcharlt |
#topic Moving the planet |
| 13:24 |
gmcharlt |
I'm inclined to back-burner that for now |
| 13:25 |
gmcharlt |
bshum: since you said that you need to leave at 1:30, if you want to bring up anything before you go... you now have the floor |
| 13:25 |
bshum |
The only thing that I keep promising to work on is getting our past IRC logs into the same logging instance that we're using now. |
| 13:26 |
bshum |
So that continues to be a longstanding side project for me. |
| 13:26 |
gmcharlt |
k |
| 13:26 |
bshum |
Past logs remain fully searchable of course, via google indexing or whatnot. But it'd just be nice if it was all ported properly. |
| 13:26 |
gmcharlt |
#action (carry-over) bshum to complete move of the old IRC logs |
| 13:27 |
gmcharlt |
kmlussier: RoganH: any new business you want to bring up before we go over the task spreadsheet? |
| 13:28 |
RoganH |
gmcharlt: Not at this time, it's been quiet on my end, at least as far as the website goes. |
| 13:28 |
kmlussier |
I have a potential blue sky item that we talked about last week - a page specifically addressing third-party integration. |
| 13:28 |
kmlussier |
Maybe it's something that can be added to the task spreadsheet. |
| 13:29 |
gmcharlt |
kmlussier: indeed, and done |
| 13:29 |
gmcharlt |
kmlussier: could you say a little more about your idea for the minutes? |
| 13:30 |
kmlussier |
I think when third-party vendors want to integrate with Evergreen, they don't really know what to do with us. Because they are used to working in a model where they contact a vendor to get a dialog started. |
| 13:31 |
kmlussier |
I'm thinking this could be a place that might describe a bit how such work can be done, how to work with a library to get the work done, who to reach out to for help. |
| 13:31 |
kmlussier |
It ideally would linke to API docs too. But I think we need to improve our documentation there too. |
| 13:33 |
kmlussier |
I think it could serve as a resource for both vendors or for libraries that want to get Evergreen to work with a particular product. |
| 13:33 |
gmcharlt |
kmlussier: ok; I've tweaked the bluesky tab just now; does that better represent your idea/ |
| 13:33 |
gmcharlt |
? |
| 13:34 |
kmlussier |
Yes, it does. |
| 13:34 |
kmlussier |
The last bit is probably a DIG thing more than a web team thing. Either way, I would be happy to work with any developer in the room on getting those API docs done. |
| 13:34 |
gmcharlt |
kmlussier++ |
| 13:35 |
gmcharlt |
jeff: ^^ the API doc discussion may be relevant to your interests |
| 13:35 |
gmcharlt |
other new items? |
| 13:37 |
gmcharlt |
#topic website task review |
| 13:37 |
gmcharlt |
so, starting from the bottom up for variety's sake |
| 13:37 |
gmcharlt |
we've mentioned the planet |
| 13:37 |
gmcharlt |
and the IRC logs |
| 13:37 |
jeff |
gmcharlt++ gracias! |
| 13:37 |
gmcharlt |
kmlussier: where do you stand with the get involved page? |
| 13:38 |
kmlussier |
gmcharlt: I think I'm done with it. |
| 13:38 |
kmlussier |
But I welcome anyone to improve, tweak, add to it. |
| 13:38 |
gmcharlt |
kmlussier: I had a feeeling... I've marked that task as completed, then |
| 13:38 |
gmcharlt |
thanks! |
| 13:38 |
kmlussier |
gmcharlt: Thank you! |
| 13:39 |
* gmcharlt |
also has too many e's, it seems |
| 13:39 |
gmcharlt |
I blame eeevil |
| 13:39 |
gmcharlt |
I think we've done what we can with the images on old blog posts, so I'm marking that complete as well |
| 13:39 |
kmlussier |
I don't know how Erica is doing with the LP page, but I might be willing to take that one on if she doesn't have the tuits. |
| 13:40 |
kmlussier |
The representative library profiles might be something the new PR committee could help with too. |
| 13:40 |
gmcharlt |
I'm not sure where she with it is either, but thanks for the offer, and I"ll leave it to you two to talk it out |
| 13:41 |
gmcharlt |
kmlussier: re the representative library profiles, sure, let us know what you find out |
| 13:42 |
gmcharlt |
hsa that committee met yet? |
| 13:42 |
RoganH |
I volunteered for it but I never heard anything about it so I don't know. |
| 13:44 |
gmcharlt |
#action (carry-over) gmcharlt will security an Akimsmet key |
| 13:44 |
kmlussier |
No, I just put out the call for volunteers last week. |
| 13:44 |
RoganH |
kmlussier: maybe I'm thinking of a past effort in that direction, my memory is of much longer past |
| 13:44 |
RoganH |
kmlussier: though I volunteered for your's too now that I think about it |
| 13:44 |
kmlussier |
RoganH: You did volunteer. I just never replied to your email. :) |
| 13:44 |
RoganH |
kmlussier: history repeats itself |
| 13:45 |
kmlussier |
Technically, the EOB is supposed to appoint members, but I think it's safe to say you're in. |
| 13:47 |
gmcharlt |
ok |
| 13:47 |
gmcharlt |
any other old business - or new business, for tha tmatter? |
| 13:49 |
kmlussier |
None from me |
| 13:49 |
jeff |
ssl certs. is that something gmcharlt and i could just work on together? |
| 13:49 |
jeff |
or does that require web team interaction/etc? |
| 13:50 |
gmcharlt |
jeff: yep, indeed, and I think you and I can just do it |
| 13:50 |
gmcharlt |
#action jeff and gmcharlt to procure SSL cert for the website |
| 13:50 |
jeff |
great. wanted to at least ask in an actual meeting, since i had the chance. :-) |
| 13:51 |
gmcharlt |
ok, last chance... |
| 13:53 |
gmcharlt |
thanks, everybody! |
| 13:53 |
gmcharlt |
#endmeeting |
| 13:53 |
pinesol_green |
Meeting ended Wed Apr 1 13:53:37 2015 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 13:53 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-04-01-13.01.html |
| 13:53 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-04-01-13.01.txt |
| 13:53 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-04-01-13.01.log.html |
| 13:54 |
kmlussier |
gmcharlt++ |
| 14:18 |
|
TaraC joined #evergreen |
| 14:22 |
|
ericar_ joined #evergreen |
| 14:23 |
csharp |
ok - so if I were to set the "Workstation Required" setting for Self Check to True, how would I create a workstation for that self-check station? |
| 14:25 |
* dbs |
is going to fork Evergreen, call it Evening, and start court challenges over the #evgils tag |
| 14:25 |
csharp |
oh - I see from the code that it should force me to register one |
| 14:25 |
eeevil |
csharp: berick can correct me if I'm wrong, but I think you reg a regular WS, then use the name in a "ws" cgi param |
| 14:27 |
csharp |
eeevil: yeah - that's right |
| 14:27 |
csharp |
it allowed me to register one |
| 14:27 |
kmlussier |
gmcharlt: I seem to recall there was something in our trademark policy that references egils. Am I remembering that correctly? |
| 14:27 |
berick |
yeah, ws=<name> is what you want. |
| 14:27 |
csharp |
eeevil: berick: thanks |
| 14:28 |
dbs |
kmlussier: http://comments.gmane.org/gmane.education.libraries.open-ils.general/7097 ? |
| 14:28 |
berick |
does look like it will let you register one right there, though |
| 14:28 |
berick |
as you said, csharp |
| 14:28 |
csharp |
yeah, it was very convenient |
| 14:28 |
kmlussier |
dbs++ |
| 14:29 |
kmlussier |
I wonder at one point #evgils becomes official enough to change the policy. |
| 14:29 |
kmlussier |
Provided that dbs doesn't win his court challenge. ;) |
| 14:30 |
|
dreuther joined #evergreen |
| 14:32 |
RoganH |
kmlussier: Does that get resolved in Canadian or US Court? |
| 14:34 |
gmcharlt |
RoganH: you're not thinking expansively enough. /Clearly/ the WIPO Abitration and Mediation Center is the appropriate venue |
| 14:35 |
RoganH |
gmcharlt: so silly of me :) |
| 14:55 |
dbs |
No no, #evgils is the whole reason I kicked off the Trans-Pacific Partnership rounds of negotiations |
| 14:56 |
dbs |
4 years of secrecy after the participants in the talks come to an agreement, during which time the involved nations have to institute the agreed-upon trade rules without informing their citizens |
| 14:56 |
dbs |
(Sadly, that is entirely true and not at all an April 1 joke) |
| 14:56 |
RoganH |
dbs: I was going to say, that's way too much a reality. |
| 14:57 |
dbs |
https://wikileaks.org/tpp-investment/press.html in case anyone feels like getting enraged |
| 14:57 |
dbs |
sorry for #offtopic |
| 15:02 |
jeff |
When transforming a 490 tag, MODS seems to construct a relatedItem of type="series" with title element that contains the 490$a and 490$v. it then seems to call out to a template to create a "part" based on subfield n, which is a 440 thing, not a 490 thing. |
| 15:02 |
jeff |
grr. |
| 15:03 |
dbs |
jeff: Is that just our frozen version of MODS, or does current MODS versions do that as well? |
| 15:03 |
jeff |
sorry, should have specified that. i'm looking at 3.5, which seems to be latest. |
| 15:04 |
dbs |
OK. They've been pretty responsive to bug reports recently, and 3.6 was just announced for testing purposes |
| 15:04 |
jeff |
behavior seems to date back to the 3.0 version, also. |
| 15:04 |
jeff |
dbs: oh, good! |
| 15:05 |
* jeff |
looks at http://www.loc.gov/standards/mods/changes-3-6.html |
| 15:05 |
dbs |
"Changes include updates to hierarchicalGeographic, relatedItem and cartographics, among others." |
| 15:05 |
dbs |
Yeah |
| 15:06 |
dbs |
They do maintain multiple versions, so entirely possible they would fix 3.something through 3.6 |
| 15:19 |
jeff |
dbs: any insight on if there is a source for the different revisions of each MODS version's marcxml -> mods xslt? |
| 15:19 |
dbs |
hahaha |
| 15:19 |
jeff |
versions 1.02 through 1.106 of http://www.loc.gov/standards/mods/v3/MARC21slim2MODS3-5.xsl, for example? |
| 15:20 |
jeff |
yeah, that's enough insight to confirm my suspicions. :-) |
| 15:20 |
dbs |
only very recently did the MODS committee acquiesce to the community requests for version control |
| 15:20 |
dbs |
(to say something like "Right, we'll look into starting to use github" |
| 15:27 |
jeff |
yeah, i've seen ksclarke/etc ask about that, but hadn't seen any positive reaction from the committee |
| 15:30 |
|
bmills joined #evergreen |
| 15:33 |
|
jwoodard_ joined #evergreen |
| 15:34 |
dbs |
http://comments.gmane.org/gmane.comp.text.mods/1656 |
| 16:02 |
|
vlewis joined #evergreen |
| 16:13 |
jeff |
dbs++ thanks! |
| 16:30 |
|
ericar_ joined #evergreen |
| 16:35 |
jeff |
dbs: no idea why that didn't show up in the listserv search i did, other than "listserv" |
| 16:39 |
|
Newziky left #evergreen |
| 16:56 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 17:11 |
|
mmorgan left #evergreen |
| 17:39 |
|
mrpeters left #evergreen |
| 18:00 |
|
dcook joined #evergreen |
| 19:21 |
|
jihpringle joined #evergreen |
| 20:52 |
|
bmills joined #evergreen |
