| Time |
Nick |
Message |
| 02:49 |
|
DPearl joined #evergreen |
| 05:13 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 08:02 |
|
rjackson-isl joined #evergreen |
| 08:13 |
|
collum joined #evergreen |
| 08:15 |
|
krvmga joined #evergreen |
| 08:16 |
krvmga |
when a patron logs into the opac and looks at their items on hold, one of the columns is labeled ACTIVATE. |
| 08:16 |
krvmga |
the code under this column is |
| 08:16 |
krvmga |
[% IF ahr.frozen == 't' AND ahr.thaw_date; |
| 08:16 |
krvmga |
date.format(ctx.parse_datetime(ahr.thaw_date), DATE_FORMAT); |
| 08:16 |
krvmga |
END %] |
| 08:16 |
krvmga |
i'm not sure what this code actually does. |
| 08:17 |
krvmga |
or why i should even display this column |
| 08:17 |
krvmga |
nothing displays in the column when i look at a hold i've placed, regardless of the hold's status (active, suspended) |
| 08:18 |
jboyer-isl |
It looks like it should be Active Date instead of Activate. |
| 08:18 |
eeevil |
krvmga: that's the date at which the hold will automatically thaw and become active |
| 08:18 |
csharp |
that says "if the hold request has been suspended, and there is a reactivation date, show the activation date" |
| 08:19 |
krvmga |
i get it. you have to add the date under "edit" and then something displays |
| 08:20 |
krvmga |
now i've made it work |
| 08:21 |
krvmga |
i'd be willing to bet that, of the million patrons in my system, there's not one that has used this. |
| 08:22 |
krvmga |
but it's good to know. thx. |
| 08:22 |
krvmga |
eeevil++ |
| 08:22 |
krvmga |
csharp++ |
| 08:22 |
csharp |
it's a very handy feature for people going out of town |
| 08:23 |
krvmga |
csharp: yes, i can see that. if i'm going on vacation and i want to suspend a hold, i want that hold to re-activate on or immediately after my return date. |
| 08:23 |
csharp |
right |
| 08:24 |
collum |
We use it for homebound patrons, as well. The staff reactivate the hold a few days before they are scheduled to go to someone's house. |
| 08:25 |
|
akilsdonk joined #evergreen |
| 08:28 |
krvmga |
collum: interesting |
| 08:38 |
krvmga |
when a patron logs into the opac and looks at the "Current Items Checked Out" screen, the barcodes and call numbers of the items are displayed. i'm not sure what the use case is for displaying these. does anyone have one? |
| 08:43 |
|
kmlussier joined #evergreen |
| 08:44 |
|
rjackson-isl joined #evergreen |
| 08:47 |
|
Shae joined #evergreen |
| 08:49 |
|
kbeswick joined #evergreen |
| 08:51 |
csharp |
krvmga: as a patron, I've sometimes wanted to be able to see the item barcode when I have similarly-titled items checked out (my county library's ILS doesn't show that) |
| 08:52 |
krvmga |
csharp: hmmm, interesting |
| 08:53 |
kmlussier |
I've had the same experience as csharp. My local library also doesn't show the barcode, but sometimes the titles that shows up in my current checkouts is identical. Usually, when my kids are reading a series. |
| 08:53 |
krvmga |
csharp: i could see a possible case for call number. maybe i like the book, got it off a display rather than from the stacks, and i'd like to browse where the shelves where this call number is. |
| 08:53 |
kmlussier |
And it's difficult to tell which one is due. |
| 08:53 |
|
mmorgan joined #evergreen |
| 08:53 |
krvmga |
kmlussier: claro |
| 09:01 |
kmlussier |
Actually, it's the call number that doesn't show in my local system. The barcode shows. I guess my previous frustration has been with not knowing which volume of a multi-volume set is due or which year of something like the Guinness Book of World Records is due. My son will often check out three years worth of Guinness within a few weeks of each other. The call number is very useful in displaying that type of info. |
| 09:13 |
bshum |
The other thing useful with CN display is dependent on cataloging practice too. In our consortium, ILL items are attached to generic bibs named like "ILL/library" with the title stuffed in CN. |
| 09:13 |
bshum |
So having it there is important for our patrons. |
| 09:15 |
|
yboston joined #evergreen |
| 09:17 |
krvmga |
thanks, everyone. this has been very helpful. |
| 09:17 |
krvmga |
bshum++ |
| 09:17 |
krvmga |
kmlussier++ |
| 09:17 |
krvmga |
csharp++ |
| 09:42 |
|
_bott_ joined #evergreen |
| 09:43 |
|
ldw joined #evergreen |
| 10:01 |
|
kmlussier left #evergreen |
| 10:02 |
|
mllewellyn joined #evergreen |
| 10:19 |
|
jwoodard joined #evergreen |
| 10:55 |
pinesol_green |
[evergreen|Remington Steed] LP#968514: Revive bib/auth importing docs from 2.1, add intro - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=cbf755b> |
| 11:00 |
yboston |
remingtron++ |
| 11:00 |
remingtron |
yboston: thanks! See how helpful deadlines can be? :) |
| 11:01 |
yboston |
absolutely |
| 11:01 |
jboyer-isl |
A note for anyone who has write access to the SIPServer repo: Sip/Configuration.pm Line 114 needs to have "LOG_WARN" changed to "LOG_WARNING". I was perplexed because my dev server wasn't allowing connections for a little bit and it wouldn't tell me why.. |
| 11:01 |
yboston |
and breaking things down into chunks, like just focusing on 2.6 new features (all great ideas from you) |
| 11:05 |
remingtron |
glad to contribute. Any word from Jennifer, Kate or Elliot? |
| 11:06 |
remingtron |
about their tasks, that is |
| 11:12 |
jeff |
jboyer-isl: i can bug and branch that. |
| 11:14 |
jboyer-isl |
jeff: Thanks. |
| 11:23 |
jeff |
jboyer-isl: what name and email address do you prefer for git attribution? |
| 11:23 |
jboyer-isl |
Jason Boyer JBoyer1 library.in.gov |
| 11:24 |
jboyer-isl |
I wasn't necessarily going to bother for 3 chars. :) |
| 11:25 |
|
vlewis joined #evergreen |
| 11:35 |
jeff |
oh and i probably just created an issue by making you author and not having a signoff from you. bah. removing you as author and crediting you in the comment message instead. :-) |
| 11:38 |
jeff |
bug 1336825 with working branch and tagged pullrequest. |
| 11:38 |
pinesol_green |
Launchpad bug 1336825 in SIPServer "Failure to log "No match" message in find_service" (affected: 1, heat: 6) [Low,New] https://launchpad.net/bugs/1336825 |
| 11:38 |
jeff |
jboyer-isl++ |
| 11:39 |
jboyer-isl |
jeff++ for helping out |
| 11:39 |
pinesol_green |
[evergreen|Erica Rohlfs] Docs: Minor wording change - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=046ad75> |
| 11:40 |
jeff |
i am yet again pondering working around some vendor software on the evergreen side of things. |
| 11:40 |
jeff |
(looking at a public workstation management package that can't do rules based on age of patron) |
| 11:41 |
jeff |
so, since it can do rules based on patron group, and since we don't otherwise use patron group at present, considering adding something to sipserver to allow it to return age-based groups. |
| 11:42 |
tsbere |
That sounds like a potentially annoying workaround if you ever do decide to use groups later. |
| 11:42 |
jeff |
right, that's one already identified potential con. |
| 11:43 |
jeff |
and one reason to continue to encourage the vendor to add the feature on their end. |
| 11:43 |
tsbere |
jeff: Can it look at arbitrary fields for specific values? |
| 11:43 |
jeff |
tsbere: pending question |
| 11:44 |
tsbere |
jeff: If the answer is "yes" then create an exported patron stat cat. Should be fairly easy to set up a DOB-based "fill that in" script that runs weekly or something. |
| 11:45 |
jeff |
trying to avoid batch update style solutions, but that would shift the location of the custom code a bit. |
| 11:49 |
|
sseng joined #evergreen |
| 12:02 |
|
tspindler joined #evergreen |
| 12:25 |
|
kmlussier joined #evergreen |
| 12:34 |
hopkinsju |
Yesterday Bmagic commited a fix for bug 1277556 into his working repo and tagged it with pullrequest on LP. Does he need to do anything else to make sure that gets noticed? |
| 12:34 |
pinesol_green |
Launchpad bug 1277556 in Evergreen "Fast Item Add no longer opens record after copy is created" (affected: 6, heat: 32) [Medium,Confirmed] https://launchpad.net/bugs/1277556 |
| 12:48 |
kmlussier |
hopkinsju: It helps to have it targeted towards a milestone. I can do that for you. |
| 12:50 |
jeff |
other than that, it looks good. key parts are: unassigned + has pullrequest tag. |
| 12:51 |
jeff |
as a matter of personal preference i like to see a real-looking first and last name and email address in the commit (both the commit/author metadata and the Signed-off-by: line, but I don't think we have that as a requirement (or even a recommendation) |
| 13:00 |
|
kitteh_ joined #evergreen |
| 13:01 |
|
ericar joined #evergreen |
| 13:04 |
|
ericar left #evergreen |
| 13:09 |
csharp |
launchpad_search-- |
| 13:17 |
|
kbeswick joined #evergreen |
| 13:19 |
|
akilsdonk joined #evergreen |
| 13:26 |
|
kbutler joined #evergreen |
| 13:29 |
|
ldwhalen joined #evergreen |
| 13:36 |
bshum |
jeff: We ought to add that somewhere as a recommendation. I agree in liking to see the full name of folks who submit. |
| 13:39 |
|
ldw_ joined #evergreen |
| 13:42 |
|
hbrennan joined #evergreen |
| 13:50 |
|
kbutler_ joined #evergreen |
| 13:51 |
yboston |
heads up, there willl be a DIG meeting at 2 PM EST |
| 13:52 |
kmlussier |
Woo hoo! |
| 13:52 |
kmlussier |
Sorry - I get a little happy at DIG meeting time. :) |
| 13:54 |
* dbs |
hears "Happy" as theme song |
| 13:55 |
bshum |
dbs: I'm sad I missed you completely at ALA. Vegas was a huge place :\ |
| 13:56 |
kmlussier |
ALA is always huge. I'm usually more surprised when I run into people I know than when I miss them. |
| 13:56 |
dbs |
bshum: I was only present at 4 sessions, really: my two, and two others on linked data |
| 13:56 |
dbs |
@blame the brother of dbs for dragging him away from the conference |
| 13:56 |
pinesol_green |
dbs: It really IS the brother of dbs's fault! for dragging him away from the conference |
| 13:56 |
dbs |
It really is! |
| 13:57 |
|
rsoulliere joined #evergreen |
| 14:00 |
yboston |
#startmeeting 2014-07-02 - DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting. |
| 14:00 |
pinesol_green |
Meeting started Wed Jul 2 14:00:24 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_07_02___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_20140702-agenda |
| 14:00 |
yboston |
#topic Introductions |
| 14:00 |
yboston |
Please feel free to start introducing yourselves... |
| 14:00 |
yboston |
#info yboston is Yamil Suarez @ Berklee college of Music - DIG meeting facilitator |
| 14:01 |
remingtron |
#info remingtron is Remington Steed, Hekman Library (Calvin College) |
| 14:01 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 14:01 |
bshum |
#info bshum is Ben Shum, Bibliomation |
| 14:01 |
kbutler |
#info kbutler is Kate Butler, Rodgers Memorial Library (NH) |
| 14:01 |
rsoulliere |
#info /me is Robert Soulliere, Mohawk College |
| 14:01 |
rsoulliere |
#info rsoulliere is Robert Soulliere, Mohawk College |
| 14:02 |
yboston |
(I will wait a few more seconds before starting) |
| 14:03 |
yboston |
OK, lets start |
| 14:03 |
yboston |
#topic any DIG memeber reports? |
| 14:03 |
yboston |
*member |
| 14:04 |
rsoulliere |
I can go |
| 14:04 |
yboston |
go ahead |
| 14:04 |
rsoulliere |
#topic Conversion Coordinator Report |
| 14:04 |
rsoulliere |
#info I updated the 2.5 upgrade instructions a few minutes ago. Updatesd in the repo so should show up tomorrow in the official docs. I hope to get the 2.6 upgrade instructions done in the next day or two. |
| 14:04 |
rsoulliere |
Beginning next week, I will be away until September so I will miss the August meeting. |
| 14:05 |
rsoulliere |
That is all. : -) |
| 14:05 |
yboston |
rsoulliere++ |
| 14:05 |
yboston |
Kathy, did you have anything to report? |
| 14:05 |
kmlussier |
Sorry, I wandered off for a minute. Sure. |
| 14:06 |
kmlussier |
#topic Release Coordinator Report |
| 14:06 |
kmlussier |
#info Nothing new to report, but I do intend to update the release notes with links to the documentation for new features. |
| 14:06 |
kmlussier |
I basically was waiting to see if new docs would be added before moving forward. |
| 14:06 |
kmlussier |
That's all I have. |
| 14:06 |
yboston |
kmlussier++ |
| 14:07 |
yboston |
At this point I suggest we move to "old business" |
| 14:07 |
remingtron |
Is there any old business? |
| 14:08 |
yboston |
as stated in the agenda, we had the entry to finsih work on 2.6 new features |
| 14:08 |
remingtron |
ah yes, that counts as old business |
| 14:09 |
yboston |
#topic Old Business |
| 14:09 |
yboston |
#topic New DIG Workflow: Document all new 2.6 features by July 1, and all new future version features by the time the version is released. |
| 14:09 |
yboston |
#info To review: All members choose 1-3 new features to document each month, emailing the list with questions and calls for help. |
| 14:09 |
yboston |
#info Progress Reports: How did this month go? Suggestions for improving the workflow? Tough features that need special attention? |
| 14:09 |
yboston |
#info Assignments: Everyone choose another 1-3 remaining new features for the next month |
| 14:10 |
yboston |
(Remington was right, this was actually listed as "priority business") |
| 14:10 |
yboston |
any comments on our overall progress, or indiviudal progress? |
| 14:10 |
kmlussier |
#link http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:2.6_needs |
| 14:11 |
remingtron |
well, now that we cleared out "old business", we don't need "priority business" |
| 14:11 |
remingtron |
I finished my marc_export docs and pushed them in, so I'm free to help others finish up |
| 14:11 |
kmlussier |
I still need to do one more thing for my task on the removal of open-ils.ingest service. gmcharlt steered me in the right direction for updating a doc that included it as an opensrf service. |
| 14:12 |
kmlussier |
I'm also free to help somebody, but not until I return from vacation on the 14th. |
| 14:12 |
kbutler |
I finished 2 of the 3 places where I needed to put the info about the new settings for staff initials. I sent it to the mailing list (today) but they haven't come through yet. |
| 14:13 |
yboston |
kbutler: which list did you use? |
| 14:13 |
kbutler |
The docs list |
| 14:13 |
kmlussier |
kbutler: Did you send it recently? I usually find my e-mail goes out on the list very quickly. |
| 14:14 |
yboston |
I don't remember seeing it either |
| 14:14 |
kbutler |
It's been a bout 30 or 45m at this point I think? A while. I haven't seen it. |
| 14:15 |
yboston |
I just checled MarkMail and I on't see it. |
| 14:15 |
yboston |
*don't |
| 14:15 |
yboston |
kbutler: I would suggest you resend it and perhaps forward it to some of us so we can have a look at it. |
| 14:15 |
kbutler |
Sure. |
| 14:16 |
kbutler |
our mail server has been screwed up this week so it's entirely possible it's stuck somewhere. :P |
| 14:16 |
yboston |
did you want to some questions now? or maybe near the end of the meeting? |
| 14:16 |
yboston |
did you want to ASK some questions now? |
| 14:17 |
yboston |
(or after the meeting, I can stay on IRC to help as much as I can |
| 14:18 |
yboston |
I just wanted to add that I was able to add a nice section on basic usage of the OPAC, as a way to add info on the 2.6 WCAG feature |
| 14:18 |
remingtron |
yboston++ |
| 14:18 |
|
ningalls joined #evergreen |
| 14:18 |
yboston |
it was some work my intern did, and I added some "search URL" stuff that I had planned to add |
| 14:18 |
yboston |
yay for deadliens |
| 14:19 |
kbutler |
yboston++ |
| 14:19 |
kmlussier |
yboston: Was that info taken from the old 1.6 docs? |
| 14:20 |
yboston |
I think so, but I think it also existed in 2.0 |
| 14:20 |
kmlussier |
yboston++ |
| 14:20 |
yboston |
now that I am getting a hang of the Git backporting, I think I can start putting a dent on adding the work the intern did |
| 14:21 |
kmlussier |
yboston++ |
| 14:21 |
yboston |
any other comments or questions about the 2.6 new features? I wish that we had some ESi folks here, but according to their poll votes, they would not make it at this time |
| 14:21 |
remingtron |
yboston: as you do, please add them to the DONE list here: |
| 14:21 |
remingtron |
http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:todo |
| 14:22 |
remingtron |
akilsdonk: do you have a minute to give us an update on ESI docs for 2.6 features? |
| 14:22 |
remingtron |
we'll see if she has time to chime in |
| 14:22 |
yboston |
I need to first add a listing of what the intern worked on, which is somewhere on the DIG wiki, and link it to the todo page |
| 14:23 |
kmlussier |
FWIW, I don't think the EDI documentation jpringle signed up for pertains to a new 2.6 feature. |
| 14:23 |
kmlussier |
At least, I can't recall any new EDI features in 2.6. |
| 14:23 |
yboston |
#action yboston will update general DIG to do list page with the work doen for 2.6 |
| 14:24 |
akilsdonk |
remingtron: the ESI docs for 2.6 are written, we just need to commit them to the repository. |
| 14:24 |
akilsdonk |
we can have them in next week. |
| 14:24 |
remingtron |
akilsdonk: great! thanks for the update |
| 14:24 |
yboston |
BTW, for those joining us late, feel free to introduce yourselves and check out the conversation log http://irc.evergreen-ils.org/evergreen/2014-07-02#i_108936 |
| 14:25 |
yboston |
to catch up |
| 14:26 |
yboston |
OK, we are at almost the half-way point. |
| 14:26 |
yboston |
Should we continue more on the 2.6 ew features, or move to something else ? |
| 14:26 |
remingtron |
I haven't heard anything from Elliot about his task in a while |
| 14:27 |
remingtron |
I'll check in with him over email and make sure it gets reassigned if needed |
| 14:27 |
remingtron |
how about we discuss plans for 2.7 and the web staff client? |
| 14:27 |
yboston |
should one of us email him directly to help him out? |
| 14:28 |
yboston |
thanks |
| 14:28 |
yboston |
#action remingtron will check in on Elliot to see if he needs help with documenting "User Editor: “Update Expire Date” button " |
| 14:29 |
yboston |
for a moment, can we go back to the Jenifer feature, so it might not be a 2.6 feature? |
| 14:30 |
yboston |
"EDI account set up" |
| 14:30 |
remingtron |
I probably added that from the preview of the release notes |
| 14:31 |
remingtron |
was it a mistake in the release notes perhaps? |
| 14:31 |
remingtron |
left over from 2.5 or something? |
| 14:31 |
kmlussier |
AFAIK, there is nothing new to the EDI accounts. I don't think it was in the release notes either. |
| 14:32 |
yboston |
we can pick a volunteer to cofirm if it was and take it out, perhaps then also start the 2.7 DIG new feature list with it |
| 14:32 |
yboston |
I can start a page for 2.7 |
| 14:33 |
kmlussier |
If you look at the history for that wiki page, there was no mention of EDI account setup until Jennifer added it as a task. |
| 14:33 |
remingtron |
based on wiki history, jihpringle added that task and assigned herself to it |
| 14:33 |
remingtron |
kmlussier: right-o |
| 14:33 |
yboston |
We can email her and coordinate to put that entry in 2.7 or the general to do page |
| 14:33 |
kmlussier |
yboston: I look at that interface all the time. I can confirm with 99.9 percent certainty that it isn't new. |
| 14:34 |
kmlussier |
Or, I should say, doesn't have anything new on it. |
| 14:34 |
yboston |
kmlussier: 99.9% coming fom you is good enough for me |
| 14:34 |
remingtron |
sure, no need to wait on that task. let's move on to 2.7 |
| 14:35 |
yboston |
I can take care of both, creating new page and moving the content |
| 14:35 |
remingtron |
I think we should get an early start on documenting the web staff client interfaces |
| 14:35 |
remingtron |
yboston++ |
| 14:35 |
remingtron |
web staff circ screens seem mostly operational now |
| 14:35 |
yboston |
#action yboston will move EDI entry from 2.6 DIG new features and put it in a new 2.7 DIG new features page; also email Jenifer to warn her |
| 14:37 |
yboston |
remingtron: I would like to run that by Bill to see if what he recommends |
| 14:37 |
remingtron |
yboston: sounds wise |
| 14:37 |
yboston |
in terms of what UI we should stay away from or which ones should stay similar |
| 14:38 |
yboston |
I gues we can start with a new section under "using the OPAC" dedicated to the new client , with proper warnings |
| 14:38 |
yboston |
that it is still in pre-realse form |
| 14:38 |
yboston |
*release |
| 14:39 |
kmlussier |
Under using the OPAC? |
| 14:39 |
remingtron |
yboston: good point, we don't want to release any docs before the web interface is released |
| 14:39 |
yboston |
I am sorry, under "using the staf client" |
| 14:39 |
kmlussier |
Ok, that sounds better. :) |
| 14:40 |
kmlussier |
I'm worried that things may still change as people offer feedback and testing begins. |
| 14:40 |
yboston |
in theory we could do it as part of an index with warnings that this is pre-release features or we can in theory create a new Git branch for syaf client documentation to be merged later? |
| 14:41 |
remingtron |
yeah, we could work in a collab branch and update things if they change |
| 14:41 |
yboston |
BTW, kbutler I see your email now |
| 14:41 |
kbutler |
yboston you may be the only one. :) |
| 14:42 |
yboston |
remingtron: yes, Git collab branch sounds like a good idea |
| 14:42 |
kmlussier |
I don't see it. |
| 14:43 |
yboston |
so I see a few things that we need to assign volunteers for right now |
| 14:43 |
remingtron |
yboston: I'll setup a collab branch and a bug report for work on the web staff client |
| 14:44 |
yboston |
remingtron: that was the first one, save me some typing |
| 14:44 |
kbutler |
kmlussier: looks like your email server decided it was spam (I got a bounceback). |
| 14:44 |
yboston |
remingtron: no matter what Bill says, it will be very god pracitce for Git to create and use a collab branch |
| 14:44 |
yboston |
but let us know what he says at this point, if that is OK with you |
| 14:45 |
yboston |
sorry, that should have said, it would be very good practice for us DIG members to use a collab branch |
| 14:45 |
remingtron |
yboston: yes, I'll ask Bill and make sure DIG knows what he recommends |
| 14:45 |
yboston |
the other dangling issue is to help kate |
| 14:46 |
yboston |
I can help her since it has to do with documenting older features, which I want to work on |
| 14:46 |
yboston |
remington: BTW< should I make the "action: or do you want to do it? |
| 14:47 |
remingtron |
I think you have to make the actions for them to stick |
| 14:47 |
yboston |
#action yboston will help kbutler with her 2.6 task "Add granular settings for requiring staff initials for notes. " |
| 14:47 |
yboston |
OK |
| 14:47 |
kbutler |
Thanks yboston |
| 14:48 |
yboston |
#action remingtron will reach out to Bill about what we can start documenting of the new browser staff client; also will experiment with setting up a Git collab brnach to work on |
| 14:49 |
yboston |
BTW, should we add an agenda item to follow up on lingering 2.6 issues for next meeting? |
| 14:49 |
kmlussier |
Sure, why not? |
| 14:50 |
yboston |
#action yboston add item to April's DIG meeting agenda about following up on ligering 2.6 new features work |
| 14:50 |
yboston |
so we are at the 50 minute mark |
| 14:51 |
remingtron |
yboston: you mean August's meeting? |
| 14:51 |
yboston |
darn it |
| 14:51 |
yboston |
#action yboston add item to August DIG meeting agenda about following up on ligering 2.6 new features work |
| 14:52 |
remingtron |
on to new business? |
| 14:52 |
yboston |
does anyone have any questions they would like to ask, specially does that have not spoken yet? A quick conversation about 2.7? |
| 14:52 |
yboston |
I was thinking of skipping new business for next meeting because of the time |
| 14:53 |
yboston |
or putting it up on the mailing list |
| 14:53 |
kmlussier |
I don't think there's much we can do for 2.7 until new features start going in. |
| 14:53 |
remingtron |
kmlussier: I think there is a lot we could do with the web staff client |
| 14:53 |
yboston |
are there any features that are "guaranteed" to be in so far? |
| 14:54 |
remingtron |
at least scoping out how much will need to be changed in the docs |
| 14:55 |
remingtron |
it might mean reading over all the circ UI docs |
| 14:55 |
kmlussier |
remingtron: Sure, I was thinking of the features unrelated to the web client. |
| 14:55 |
remingtron |
kmlussier: right, then I agree |
| 14:55 |
yboston |
bshum: hypothetically are there any features that are "guaranteed" to be in 2.7 so far? so we can start trying to prepare the docs already |
| 14:56 |
yboston |
bshum: it might be way to early for alost any new 2.7 feature, but wondering if something was definetly going |
| 14:56 |
yboston |
*almost |
| 14:57 |
yboston |
I guess, we can look into working on older features while we wait for the 2.7 features to be finalized |
| 14:57 |
yboston |
I can send an email to the list to slect amonst ourselves some older features to work on, hopefull we can get newcomers involved too |
| 14:58 |
remingtron |
yboston: yeah, let's focus on older features and web staff client updates now, then hopefully switch to new features as they come |
| 14:58 |
yboston |
OK |
| 14:58 |
kmlussier |
yboston: This list will give you an idea of what might be eligible for 2.7 http://bit.ly/1qyGrOx |
| 14:59 |
kmlussier |
But until the code is tested, I don't think there's any guarantee that anything will definitely make the cut. |
| 14:59 |
yboston |
thanks |
| 14:59 |
yboston |
kmlussier: yes, without testing nothing should be guranteed |
| 15:00 |
kmlussier |
So should we each commit to 1 to 3 features from the 2.5 list between now and the next meeting? |
| 15:00 |
yboston |
you read my mind |
| 15:00 |
* kmlussier |
is psychic. :) |
| 15:00 |
remingtron |
+1 |
| 15:01 |
kbutler |
+1 |
| 15:01 |
yboston |
#action yboston start a thread on DIG mailing list on targeting small older docuemntation tasks for the month of July; like working on 1 to 3 features from the 2.5 list between now and the next meeting? |
| 15:01 |
remingtron |
we're making progress! I'm so excited! |
| 15:02 |
yboston |
it is 3:01 PM EST, any last thoughts or do we want to keep going? |
| 15:02 |
yboston |
also, kbutler I am free to chat after the meeting if you want |
| 15:02 |
remingtron |
I think we're ready to finish |
| 15:02 |
yboston |
though I need to review your email carefully first |
| 15:02 |
kbutler |
Sure. I'll be around for a bit. |
| 15:02 |
yboston |
I think so too, but always like to offer a choice |
| 15:03 |
yboston |
#endmeeting |
| 15:03 |
pinesol_green |
Meeting ended Wed Jul 2 15:03:16 2014 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 15:03 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-07-02-14.00.html |
| 15:03 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-07-02-14.00.txt |
| 15:03 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-07-02-14.00.log.html |
| 15:04 |
yboston |
kbutler: I need to update the past DIG meetinginformation page now. let me get back to you either later today or tomorrow on your email. |
| 15:05 |
jeff |
DIG++ |
| 15:05 |
|
rsoulliere left #evergreen |
| 15:05 |
kbutler |
yboston: sounds good. |
| 15:05 |
* tsbere |
is amused about being included in a list of people that might be responsible for ESI's print/marketing materials in this email he just received |
| 15:10 |
jcamins |
tsbere: but you *might* be! |
| 15:10 |
jcamins |
Are you sure you aren't? |
| 15:11 |
tsbere |
I was the only non-esi recipient |
| 15:12 |
kmlussier |
tsbere: Maybe the sender just assumed you all worked for "evergreen"? |
| 15:13 |
tsbere |
The email specifically says "Equinox's" |
| 15:18 |
jcamins |
tsbere: no wonder ESI staff are so desperate for pens! |
| 15:29 |
eeevil |
jcamins: hey, they're great pens! http://blog.librarything.com/thingology/2013/10/the-librarything-conference-pen-olympics/ |
| 15:31 |
jcamins |
eeevil: wow, tsbere is doing a great job without even noticing it! |
| 15:36 |
graced |
tsbere: That *was* a weird email... I was wondering if it was someone you recommended to us or something since we have never heard of that guy. |
| 15:37 |
tsbere |
graced: I had nothing to do with it and likely found it more weird than you did. |
| 15:38 |
graced |
Indeed. I can imagine being lumped in with me and eeevil is weird for many. |
| 15:39 |
tsbere |
I was thinking being lumped in as though I were an employee of a company that I don't work for. I would have thought they might have figured out something was wrong when the domain of my email address didn't match the pattern. |
| 15:41 |
graced |
That would be the first obvious thing, wouldn't it? |
| 16:31 |
|
kmlussier1 joined #evergreen |
| 16:35 |
|
tspindler left #evergreen |
| 16:37 |
|
ningalls joined #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> |
| 16:58 |
|
kbutler_ joined #evergreen |
| 17:13 |
|
mmorgan left #evergreen |
| 17:15 |
|
kmlussier left #evergreen |
| 17:24 |
|
jwoodard joined #evergreen |
| 17:32 |
|
kbutler joined #evergreen |
| 20:23 |
|
dcook joined #evergreen |
| 23:21 |
|
zerick joined #evergreen |
