#duraspace IRC Log


IRC Log for 2011-10-26

Timestamps are in GMT/BST.

[6:27] -holmes.freenode.net- *** Looking up your hostname...
[6:27] -holmes.freenode.net- *** Checking Ident
[6:27] -holmes.freenode.net- *** Found your hostname
[6:27] -holmes.freenode.net- *** No Ident response
[6:27] * DuraLogBot (~PircBot@atlas.duraspace.org) has joined #duraspace
[6:27] * Topic is '[Welcome to DuraSpace - This channel is logged - http://irclogs.duraspace.org/]'
[6:27] * Set by cwilper!ad579d86@gateway/web/freenode/ip. on Fri Oct 22 01:19:41 UTC 2010
[10:25] * grahamtriggs (~Graham@host213-123-239-134.in-addr.btopenworld.com) has joined #duraspace
[11:02] * grahamtriggs (~Graham@host213-123-239-134.in-addr.btopenworld.com) has left #duraspace
[12:07] * mhwood (~mhwood@2001:18e8:3:10ab:7a2b:cbff:feb4:89a9) has joined #duraspace
[12:54] * tdonohue (~tdonohue@c-98-228-58-145.hsd1.il.comcast.net) has joined #duraspace
[13:25] * grahamtriggs (~Graham@host213-123-239-134.in-addr.btopenworld.com) has joined #duraspace
[14:06] * tdonohue (~tdonohue@c-98-228-58-145.hsd1.il.comcast.net) Quit (Ping timeout: 240 seconds)
[14:43] * tdonohue (~tdonohue@c-98-228-58-145.hsd1.il.comcast.net) has joined #duraspace
[16:46] * grahamtriggs (~Graham@host213-123-239-134.in-addr.btopenworld.com) Quit (Read error: Connection reset by peer)
[17:16] * cbeer (~cbeer@ Quit (Read error: Connection reset by peer)
[17:16] * cbeer (~cbeer@ has joined #duraspace
[19:35] * anj (~Adium@cpc12-seac20-2-0-cust1.7-2.cable.virginmedia.com) has joined #duraspace
[19:41] * anj (~Adium@cpc12-seac20-2-0-cust1.7-2.cable.virginmedia.com) Quit (Remote host closed the connection)
[19:44] * anj (~Adium@cpc12-seac20-2-0-cust1.7-2.cable.virginmedia.com) has joined #duraspace
[19:46] * anj (~Adium@cpc12-seac20-2-0-cust1.7-2.cable.virginmedia.com) Quit (Remote host closed the connection)
[19:47] * anj (~Adium@cpc12-seac20-2-0-cust1.7-2.cable.virginmedia.com) has joined #duraspace
[19:48] * anj (~Adium@cpc12-seac20-2-0-cust1.7-2.cable.virginmedia.com) Quit (Remote host closed the connection)
[19:52] <tdonohue> Hi all, reminder we've got our DSpace Developers Mtg here at the top of the hour: https://wiki.duraspace.org/display/DSPACE/DevMtg+2011-10-26
[19:52] <kompewter> [ DevMtg 2011-10-26 - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DevMtg+2011-10-26
[19:55] * anj (~Adium@cpc12-seac20-2-0-cust1.7-2.cable.virginmedia.com) has joined #duraspace
[19:56] * anj (~Adium@cpc12-seac20-2-0-cust1.7-2.cable.virginmedia.com) has left #duraspace
[19:59] * KevinVdV (~KevinVdV@d54C156FD.access.telenet.be) has joined #duraspace
[19:59] <KevinVdV> Hi all
[20:00] <tdonohue> Hi KevinVdV & all.
[20:00] * anj (~Adium@cpc12-seac20-2-0-cust1.7-2.cable.virginmedia.com) has joined #duraspace
[20:00] <tdonohue> Ok, looks like it's time for our normal DSpace Devel Mtg. Today's agenda is up at: https://wiki.duraspace.org/display/DSPACE/DevMtg+2011-10-26
[20:00] <kompewter> [ DevMtg 2011-10-26 - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DevMtg+2011-10-26
[20:01] <tdonohue> First & foremost, 1.8.0 updates. (Robint is off on holiday this week, fyi)
[20:02] <tdonohue> I was curious if anyone has any "outstanding" issues to still be resolved for 1.8.0? Trying to nail down whether we try for release this week (Oct 28th), or if we push back one more week until robint returns (Nov 4).
[20:02] <KevinVdV> Well I have something that still requires testing
[20:02] * hpottinger (80cea2c6@gateway/web/freenode/ip. has joined #duraspace
[20:03] <tdonohue> what requires testing KevinVdV?
[20:03] <KevinVdV> DS-599
[20:03] <kompewter> [ https://jira.duraspace.org/browse/DS-599 ] - [#DS-599] SOLR statistics file download displays all files and not only those in the Bundle Original - DuraSpace JIRA
[20:03] <KevinVdV> RobinT tested it on the DSpace demo server & it worked there
[20:03] <KevinVdV> But it was hardly a couple of 1000 records to update
[20:04] <KevinVdV> So I would like somebody with a HUGE solr to attempt the update script to ensure no out of memory errors occur
[20:04] <KevinVdV> I tested it with 200 000 records but my machine had 12GB of ram
[20:05] * jose_blanco (8dd32b9d@gateway/web/freenode/ip. has joined #duraspace
[20:05] <tdonohue> Anyone have a larger solr data set that would be willing to help KevinVdV to test out Ds-599? PeterDietz, are you around (I recall you had OutOfMemory issues previously -- be go to see if those are now fixed)?
[20:05] <kshepherd> i can generate a huge index rather quickly ;)
[20:05] <kshepherd> i'm happy to help test this. i was meaning to put my hand up last week but had too much else on
[20:05] <PeterDietz> hi all.
[20:06] <KevinVdV> Great thanks ksheperd
[20:06] <PeterDietz> yes, I've been meaning to test it. I've reported problems on previous patches
[20:06] <tdonohue> thanks, kshepherd. That'd be good. (others are still welcome to test as well -- be good to ensure this is resolved once & for all)
[20:07] <PeterDietz> I don't know any way to pass my system information around (assuming I didn't mind you having access to our db+solr)
[20:07] <tdonohue> PeterDietz & kshepherd -- will you both be able to test it sometime this week? It'd be good to test this *before* 1.8.0 final (and not after) :)
[20:07] <mhwood> IIRC there is a tool to generate as much log data as you want.
[20:08] <KevinVdV> Should problems occur log them in the JIRA & I will attempt to resolve them as quickly as I can
[20:09] <kshepherd> tdonohue: yep will try my best
[20:09] <tdonohue> ok, thanks. would really like to ensure we are good with this before 1.8.0 (otherwise, we'd likely need to release an immediate 1.8.1 to fix issues)
[20:10] <KevinVdV> Indeed tdonohue that is the reason why I keep bugging you guys about it
[20:10] <tdonohue> mhwood -- do you have a name of that tool? Might be a good general resource for us for testing log related stuff (so, if you find it, send it along)
[20:11] <tdonohue> Ok, any other outstanding issues for 1.8.0?
[20:11] <mhwood> org.dspace.statistics.util.StatisticsDataGenerator
[20:12] <tdonohue> mhwood -- oh, yea, thanks. I forgot we had that (slaps forehead) :)
[20:13] <tdonohue> One other issue I've discovered -- not sure if it's a bug or not. (1) 'ant update' and (2) 'ant -Dconfig=[path-to-dspace.cfg] update' behave slightly differently. The former (#1) replaces your old dspace.cfg with a new one. While the latter (#2) does not.
[20:14] <mhwood> I would prefer and expect that (2) also replaces the .cfg
[20:15] <tdonohue> yea, that's what I initially expected as well. So, I guess others agree this is likely a "bug"? (if so, I can re-open DS-1060, which robint closed already)
[20:15] <kompewter> [ https://jira.duraspace.org/browse/DS-1060 ] - [#DS-1060] When running &#39;ant update&#39; copy dspace.cfg to *.old in line with all the other config files - DuraSpace JIRA
[20:15] <tdonohue> Also, I've looked into this issue a bit yesterday & I'm not sure if there is an easy fix or not. So, if anyone has ideas, I'd love more "eyes" on this problem. It's rather annoying to me.
[20:16] <PeterDietz> I was just thinking, that I don't know if anyone has tested DS-528 - Podcasts
[20:16] <kompewter> [ https://jira.duraspace.org/browse/DS-528 ] - [#DS-528] RSS feeds to support richer features, such as iTunes Podcast or Media RSS - DuraSpace JIRA
[20:17] * mhwood makes a note to look into ant problem
[20:17] <PeterDietz> It works for us having an audio collection, however there are other materials that could be podcastable, and I haven't tested the case of someone podcasting PDF's into iTunes
[20:18] <hpottinger> todonohue: I'll look into the ant issue, too
[20:18] <tdonohue> thanks mhwood & hpottinger. I could really use the help. I'll reopen Ds-1060 & put my findings there (so feel free to add your own findings as well)
[20:19] <tdonohue> Anyone willing to help PeterDietz to do some more testing of Ds-528? Or anyone already done some testing & found it to have worked fine?
[20:19] <hpottinger> been meaning to play with 528, but haven't gotten to it, yet
[20:20] <tdonohue> Any chance you (or others) could get to it later this week, or early next week? (Trying to nail down our release timelines -- I'd obviously love to get this stuff all "tested" before we release 1.8.0)
[20:21] <PeterDietz> ...especially if that one is possibly one of the "What's New" features
[20:21] <PeterDietz> i'll do some more testing of it.. and look for potential problems
[20:21] <hpottinger> I'll add it to the list
[20:21] <PeterDietz> I haven't visited that code in a while
[20:22] <PeterDietz> I have a not-quite-bug to report. XMLUI doesn't report the result text for all items that it runs curation task on.. but running curation via CLI reports results just fine
[20:23] * mdiggory (~mdiggory@rrcs-74-87-47-114.west.biz.rr.com) has joined #duraspace
[20:23] <PeterDietz> P.S. Google Mentor's summit was alot of fun. I got to meet Bojan
[20:24] <tdonohue> PeterDietz -- yea, that's a known thing with Curation Tasks. It *logs* everything it interacted with though -- but the UI doesn't do the best at reporting everything, yet. I think we may just have to "live with it" for 1.8.0 in that case.
[20:24] <tdonohue> PeterDietz -- That's great! Glad that GSoC Mentor's summit was fun! I had forgotten that it was this past weekend
[20:25] <PeterDietz> ...our baby got bad jetlag, both ways, so I'm just catching up on sleep. PSS taking a red-eye home, and then working the following day is not fun
[20:25] <tdonohue> Ok, so the latest status with 1.8.0 then seems to be: Everything is "mostly done". But, DS-528 & DS-599 need more testing (we had several volunteers for each). While DS-1060 needs fixing (we also had several volunteers to help chip in). So, we are almost done here
[20:25] <kompewter> [ https://jira.duraspace.org/browse/DS-528 ] - [#DS-528] RSS feeds to support richer features, such as iTunes Podcast or Media RSS - DuraSpace JIRA
[20:26] <kompewter> [ https://jira.duraspace.org/browse/DS-599 ] - [#DS-599] SOLR statistics file download displays all files and not only those in the Bundle Original - DuraSpace JIRA
[20:26] <kompewter> [ https://jira.duraspace.org/browse/DS-1060 ] - [#DS-1060] When running &#39;ant update&#39; copy dspace.cfg to *.old in line with all the other config files - DuraSpace JIRA
[20:27] <tdonohue> But, because of the testing & fixes that we just discussed, it sounds like we unfortunately need to push back another week & release 1.8.0 *next week*
[20:27] <tdonohue> Does everyone feel comfortable with that? (this does however mean that we all need to try and help test & fix the above three issues this week & early next week, if possible)
[20:28] <hpottinger> and documentation :-)
[20:28] <tdonohue> It would just be really good to get 1.8.0 nailed down. This is the 2nd or 3rd delay already -- I'd hate to keep slipping back another week and another week, etc.
[20:29] <tdonohue> yea, Documentation as well!
[20:30] <tdonohue> What do others think about this? Is it reasonable to get these 3 issues tested/fixed before say end-of-day on Monday, Oct 31? I'd also like everyone to help read/skim through some of our docs, if you get a chance before then.
[20:31] <tdonohue> (obviously by "reasonable" I'm assuming we don't find major issues/bugs. If we do, then that would require us to push back again and fix them ASAP)
[20:32] <KevinVdV> Well I can say that if people can test DS- 599 I can attempt to small fix issues found quickly
[20:32] <hpottinger> I think this all sounds reasonable
[20:33] * mhwood adding "by 31st" to my note.
[20:34] <tdonohue> others? PeterDietz, kshepherd? (as you were all volunteers above) sound reasonable to get this "done" by end-of-day on Oct 31st?
[20:35] <PeterDietz> I'll test these 2 today (podcast, bitstream solr)
[20:36] <tdonohue> thanks PeterDietz
[20:36] <tdonohue> I'm assuming others are OK with this. If you are not, please speak up. If you can offer more help, also please speak up.
[20:37] <tdonohue> Note for kshepherd -- I think we still need documentation from you around the new Curation tasks (Link Checker, MS Translator, etc.)
[20:37] <tdonohue> ok, moving on to Documentation in general... I posted a few ideas for how we could "release" our 1.8.0 Wiki Docs to the agenda: https://wiki.duraspace.org/display/DSPACE/DevMtg+2011-10-26
[20:37] <kompewter> [ DevMtg 2011-10-26 - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DevMtg+2011-10-26
[20:38] <tdonohue> The two ideas are: (1) we move all the content from DSDOCDEV -> DSDOC (overwriting what is currently in DSDOC, or moving it elsewhere)
[20:39] <tdonohue> OR, (2) we move the content from DSDOCDEV to a new space "DSDOC18" (for 1.8). This is the model that Fedora & DuraCloud have started to take for their docs, as it's less "overwriting" and easier to manage in Confluence
[20:39] <tdonohue> For example, Fedora has their recent 3.5 docs at: https://wiki.duraspace.org/display/FEDORA35 and their older 3.4 docs at: https://wiki.duraspace.org/display/FEDORA34
[20:39] <kompewter> [ Fedora 3.5 Documentation - Fedora 3.5 Documentation - DuraSpace Wiki ] - https://wiki.duraspace.org/display/FEDORA35
[20:39] <kompewter> [ Fedora 3.4 Documentation - Fedora 3.4 Documentation - DuraSpace Wiki ] - https://wiki.duraspace.org/display/FEDORA34
[20:40] <tdonohue> we could do something similar, and move our 1.7 docs to "DSDOC17" and have the 1.8 docs at "DSDOC18", if we wanted.
[20:40] <mhwood> Confused. Doesn't DSDOC already contain multiple versions? Wouldn't we just copy the content from DSDOCDEV to make one more?
[20:40] <tdonohue> I'm just curious here if anyone has any real "preferences" here.
[20:40] <hpottinger> 2 seems safer, and duplicates the historical document nature that was previously provided by the embedded documenation
[20:41] <PeterDietz> so if we have available versions, is there any way to have DSDOC be a link to the latest version, to avoid breaking any links to documentation
[20:41] <tdonohue> mhwood -- DSDOC is the docs for 1.7.x essentially. So, it doesn't cover DSpace 1.6.x, nor 1.8.x (obviously)
[20:42] * hpottinger_ (80cea2c6@gateway/web/freenode/ip. has joined #duraspace
[20:42] <tdonohue> what I'm suggesting is potentially the following. Move DSDOC content to DSDOC17 (docs for 1.7.x). Move DSDOCDEV to DSDOC18 (docs for 1.8.x). From this point forward always create a new space for new versions of docs. So, hypothetically, the docs for DSpace 7.0 would be at DSDOC70, etc.
[20:44] <tdonohue> if we don't like this idea, we can try and keep around a "DSDOC" which is always the *latest version*. But, even doing that doesn't guarrantee that we won't "break links" -- e.g. if we change the name of a page in the Documentation between 1.7 and 1.8, then the older "1.7-style" DSDOC links may break.
[20:44] <mhwood> Ah. What we have is static renderings of earlier releases' documentation, a "space" containing 1.7.x documentation, and another "space" containing 1.8.x documentation. We're already doing the multiple "spaces" and we just need to adjust some names. Right?
[20:45] * hpottinger (80cea2c6@gateway/web/freenode/ip. Quit (Ping timeout: 265 seconds)
[20:45] <mhwood> (Confused looking at https://wiki.duraspace.org/display/DSPACE/DSpaceResources#DSpaceResources-DocumentationandGuides, which has links all the way back to 1.5.0, but they go to another server.)
[20:45] <kompewter> [ DSpaceResources - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DSpaceResources#DSpaceResources-DocumentationandGuides,
[20:45] <mhwood> BTW that page also says that the latest doc.s are available in SVN.
[20:45] <tdonohue> mhwood -- correct. Right now it's all about adjusting some space names. But, in the future, we will have a "standard" naming convention of "DSDOCxx" where "xx" refers to the major version number (e.g. "1.8.0 = DSDOC18"
[20:47] <hpottinger_> could possibly redirect DSDOC to whatever the current stable version number is
[20:47] <tdonohue> mhwood -- that DSpaceResources wiki page does have old links that go to another server -- cause those docs don't exist anywhere on our wiki. In the future it would just link to the appropriate wiki section
[20:47] <tdonohue> hpottinger -- yea, we may be able to look into redirecting DSDOC to current stable version. Or putting up a splash page which just links you off to all the available versions of DSpace Documentation.
[20:48] <hpottinger_> I like the splash page redirect idea
[20:49] <tdonohue> So, that would mean we'd do the following: (a) DSDOC content moves to DSDOC17. (b) DSDOCDEV content moves to DSDOC18 (c) create a new version of DSDOC which just links off to all available versions of DSpace Docs (and potentially tries to redirect you if we can figure out how to do that)
[20:50] <tdonohue> Does this sound OK to everyone? I didn't want to jump in and just start moving around documentation without running it by everyone else. So, if you disagree or are confused, let me know
[20:51] <mhwood> As long as people don't have to chase "current" as the software evolves, it sounds okay to me.
[20:53] <hpottinger_> of course, the splash page redirect would have to be careful about what it decides to reuse of the user's input... would be a perfect place for XSS attacks
[20:53] <PeterDietz> hmm, gotta put my SEO hat on to think if creating multiple copies of the docs will hurt things too much, there's no way for GoogleBot to know to show you dsdoc18 over dsdoc17
[20:54] <PeterDietz> ...but i was just thinking that would should also publish the latest javadoc to projects....
[20:54] <tdonohue> PeterDietz -- yea, that's true. But at the same time, what good does DSpace 1.8 docs do you if you are looking for 1.7 docs? (i.e. if DSDOC is always just the latest version of docs, how do you ever find old versions?)
[20:55] <PeterDietz> ideally, it would all be inside of dsdoc, and I can choose from a dropdown to view a previous version... But i think that might be a limitation of confluence
[20:55] <tdonohue> If you all want to see an example of this...take a closer look at what Fedora has done. For example, in their *old* documentation (for 3.4) you'll notice it has a "NOTICE" at the top of the page which links you off to all available versions (to let you find the appropriate version): https://wiki.duraspace.org/display/FEDORA34/Fedora+3.4+Documentation
[20:55] <kompewter> [ Fedora 3.4 Documentation - Fedora 3.4 Documentation - DuraSpace Wiki ] - https://wiki.duraspace.org/display/FEDORA34/Fedora+3.4+Documentation
[20:56] * jose_blanco (8dd32b9d@gateway/web/freenode/ip. Quit (Quit: Page closed)
[20:56] <hpottinger_> could link to the newer docs from each page of the older docs (footer), that should raise the rank of the new dos, yes?
[20:56] <tdonohue> Also, with Fedora, you'll see they have a left-sidebar set up to let you jump between versions of docs
[20:57] <tdonohue> The *current* release of Fedora docs is noted by a "green bar" at the top -- but, it still provides you with a link to find other versions: https://wiki.duraspace.org/display/FEDORA35/Fedora+3.5+Documentation
[20:57] <kompewter> [ Fedora 3.5 Documentation - Fedora 3.5 Documentation - DuraSpace Wiki ] - https://wiki.duraspace.org/display/FEDORA35/Fedora+3.5+Documentation
[20:58] <tdonohue> So, I was thinking of doing something *similar* to what Fedora has done. Fedora in turn basically copied this concept from Atlassian (makers of Confluence), as this is how they manage their docs in Confluence
[20:59] <tdonohue> hpottinger_: yea, confluence provides a way to auto-link older docs to newer docs (or visa versa). Notice that the headers our DSDOCDEV space all link back to "view this same page in the current documentation": https://wiki.duraspace.org/display/DSDOCDEV/DSpace+Documentation
[20:59] <kompewter> [ DSpace Documentation - DSpace Unreleased Documentation - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSDOCDEV/DSpace+Documentation
[21:00] <PeterDietz> Tim, I think your plan is fine. Java's javadocs over at Oracle, just have a number javase/1.4.2/docs, 1.5.0, 6, 7
[21:00] <hpottinger_> I frankly really like the proposed approach
[21:01] <tdonohue> cool :) again, really just wanted to bounce this around, since we are getting near the end of 1.8.0 and need to move the DSDOCDEV content somewhere else anyways
[21:01] <PeterDietz> ...no javase/latest/docs, but there is a splash page that says click here for 4, 5, 6, or 7
[21:03] <tdonohue> ok, it sounds like most (at least those who are being vocal) think this sounds good. So, I'll start moving in this direction for 1.8.0. But, I'll send an email to dspace-devel before I actually move anything around (just as a warning to everyone)
[21:04] <tdonohue> Beyond that, I think 1.8.0 is doing well. Please trying & get your testing & fixes & docs review completed by end-of-day on Monday, Oct 31 (as requested above). Robint & I will then work on doing the 1.8.0 release mid-to-late next week.
[21:05] <tdonohue> That's everything I had for today & we are running over, I see. So, the meeting is adjourned. But, feel free to hang out if you have other topics you want to bring up, etc.
[21:05] <tdonohue> I'll stick around here for a bit.
[21:06] * mdiggory (~mdiggory@rrcs-74-87-47-114.west.biz.rr.com) Quit (Quit: mdiggory)
[21:06] <KevinVdV> Sorry guys but really need to go, need some sleep
[21:07] <KevinVdV> Until next week guys
[21:07] <mhwood> Sleep, then! I must go too.
[21:07] * KevinVdV (~KevinVdV@d54C156FD.access.telenet.be) Quit (Quit: KevinVdV)
[21:08] * mhwood (~mhwood@2001:18e8:3:10ab:7a2b:cbff:feb4:89a9) has left #duraspace
[21:18] * hpottinger_ (80cea2c6@gateway/web/freenode/ip. Quit (Quit: Page closed)
[21:23] * anj (~Adium@cpc12-seac20-2-0-cust1.7-2.cable.virginmedia.com) Quit (Quit: Leaving.)
[21:32] * anj (~anj@cpc12-seac20-2-0-cust1.7-2.cable.virginmedia.com) has joined #duraspace
[21:39] * mdiggory (~mdiggory@ip72-199-216-7.sd.sd.cox.net) has joined #duraspace
[21:58] * tdonohue (~tdonohue@c-98-228-58-145.hsd1.il.comcast.net) Quit (Read error: Connection reset by peer)
[22:24] * anj (~anj@cpc12-seac20-2-0-cust1.7-2.cable.virginmedia.com) Quit (Read error: Connection reset by peer)
[22:24] * anj_ (~anj@ has joined #duraspace
[23:49] * mdiggory (~mdiggory@ip72-199-216-7.sd.sd.cox.net) Quit (Quit: mdiggory)

These logs were automatically created by DuraLogBot on irc.freenode.net using the Java IRC LogBot.