Timestamps are in GMT/BST.
[6:42] -cameron.freenode.net- *** Looking up your hostname...
[6:42] -cameron.freenode.net- *** Checking Ident
[6:42] -cameron.freenode.net- *** Found your hostname
[6:42] -cameron.freenode.net- *** No Ident response
[6:42] * DuraLogBot (~PircBot@atlas.duraspace.org) has joined #duraspace
[6:42] * Topic is '[Welcome to DuraSpace - This channel is logged - http://irclogs.duraspace.org/]'
[6:42] * Set by cwilper!ad579d86@gateway/web/freenode/ip.184.108.40.206 on Fri Oct 22 01:19:41 UTC 2010
[13:07] * tdonohue (~email@example.com) has joined #duraspace
[15:14] * hpottinger (~firstname.lastname@example.org) has joined #duraspace
[18:48] * jrgriffiniii (~email@example.com) Quit (Remote host closed the connection)
[19:02] * helix84 (~firstname.lastname@example.org) has joined #duraspace
[19:07] * pbecker (~rooms@2001:6f8:900:8f1c:7401:7743:bc2e:c899) has joined #duraspace
[19:23] * bollini (~email@example.com) has joined #duraspace
[19:28] * bollini (~firstname.lastname@example.org) Quit (Ping timeout: 248 seconds)
[19:51] * awoods (~email@example.com) has joined #duraspace
[19:53] * PeterDietz (~firstname.lastname@example.org) has joined #duraspace
[19:53] * robint (5eaf588c@gateway/web/freenode/ip.220.127.116.11) has joined #duraspace
[19:57] * bollini (~email@example.com) has joined #duraspace
[19:58] * kstamatis (2ebe5dfb@gateway/web/freenode/ip.18.104.22.168) has joined #duraspace
[20:00] * jrgriffiniii (~firstname.lastname@example.org) has joined #duraspace
[20:01] <tdonohue> Hi Developers, it's time for our weekly DSpace Developers Mtg. Agenda: https://wiki.duraspace.org/display/DSPACE/DevMtg+2013-10-02
[20:01] <kompewter> [ DevMtg 2013-10-02 - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DevMtg+2013-10-02
[20:01] <tdonohue> we'll start things off with our using PR reviews
[20:02] <tdonohue> kicking off today with #297 / DS-1654 : https://github.com/DSpace/DSpace/pull/297
[20:02] <kompewter> [ DS-1654 by jpiscanc · Pull Request #297 · DSpace/DSpace · GitHub ] - https://github.com/DSpace/DSpace/pull/297
[20:02] <kompewter> [ https://jira.duraspace.org/browse/DS-1654 ] - [#DS-1654] IP-Based authentication fails if load-balancer/proxy - DuraSpace JIRA
[20:03] * StuartLewis (~email@example.com) has joined #duraspace
[20:04] * hpottinger cheers for the Edinburgh crew
[20:04] <bollini> look good, not sure about security implications
[20:05] * l_a_p (~firstname.lastname@example.org) has joined #duraspace
[20:05] <bollini> we should suggest a more standard name for the configuration parameter (English folks please help)
[20:05] * vtkeithg (~email@example.com) has joined #duraspace
[20:06] <hpottinger> perhaps "proxy" is a more generic term?
[20:06] <helix84> wait, we already have such config property
[20:07] * StuartLewis (~firstname.lastname@example.org) Quit (Client Quit)
[20:07] <tdonohue> proxy does seem like a better term here
[20:07] <bollini> mmm, I think that here we have done some wrong
[20:08] <bollini> proxy was introduced to allow dspace to see the external world
[20:08] * aschweer (~email@example.com) has joined #duraspace
[20:08] <bollini> here we are talking about a load-balancer so dspace see user as coming from a single ip
[20:09] <helix84> it slipped my mind what it's called
[20:09] <bollini> there are case where dspace need a proxy but is not behind a load-balancer and viceversa
[20:10] <aschweer> we have xmlui.controlpanel.activity.ipheader = X-Forward-For which is triggered by useProxies = true
[20:10] <helix84> useProxies
[20:10] <helix84> yes :)
[20:12] <tdonohue> I admit this is an area of DSpace I'm not as familiar with..mostly cause I've never set it up to use proxies. But, is there someone here who would like to add comments on PR #297 and help it get in? The idea seems good, i just don't know what to suggest myself
[20:12] <helix84> # If enabled, the logging and the solr statistics system will look for
[20:12] <helix84> # an X-Forward header. If it finds it, it will use this for the user IP address
[20:12] <helix84> #useProxies = true
[20:14] <helix84> bollini: what you call load balancer can be also called a reverse proxy and it can pass X-Forwarded-For headers, too. E.g. Squid can.
[20:14] <bollini> helix84: yes
[20:15] <bollini> probably we only need to clarify better the documentation
[20:15] <helix84> bollini: so, is there anything that concerns you?
[20:15] <bollini> check this old version, not able to find in the current documentation http://www.dspace.org/1_6_0Documentation/ch05.html#N12E28
[20:15] <kompewter> [ Chapter 5. DSpace System Documentation: Configuration ] - http://www.dspace.org/1_6_0Documentation/ch05.html#N12E28
[20:16] <aschweer> But according to the commit message, DSpace currently assumes that X-Forwarded-For is a comma-separated list while it appears to be passed in as an Enumeration instead. That sounds like a bug to me, not lack in documentation.
[20:17] <helix84> bollini: http.proxy.host is used in case when DSpace is behind a regular (not reverse) proxy
[20:17] <bollini> I was confused about the useProxy settings I had guest that it come from http.proxy.host I had missed that we have a different parameter for that... so sorry for the confusion
[20:17] <tdonohue> this ticket/PR sounds like it needs more eyes in general. I'm wondering if we should table it so that a few folks can look at it "offline" and report back? Anyone willing to take a closer look?
[20:18] <helix84> aschweer: good catch, could you please create a Jira issue so that we don't forget about it?
[20:19] <aschweer> helix84: I thought https://jira.duraspace.org/browse/DS-1654 already says so :)
[20:19] <kompewter> [ [#DS-1654] IP-Based authentication fails if load-balancer/proxy - DuraSpace JIRA ] - https://jira.duraspace.org/browse/DS-1654
[20:19] <kompewter> [ https://jira.duraspace.org/browse/DS-1654 ] - [#DS-1654] IP-Based authentication fails if load-balancer/proxy - DuraSpace JIRA
[20:19] <aschweer> I'm happy to have a look at this. we're not using load balancing but I can spin up a squid if necessary
[20:19] <tdonohue> As we are already nearly 20 mins into the meeting, I'm gonna suggest we move along here (rather then spend too much more time on this one PR)
[20:20] <helix84> aschweer: Right, sorry. I didn't see the forest for the trees.
[20:20] <aschweer> helix84: all good :)
[20:20] <tdonohue> And I'm also gonna move us along to the main part of the agenda (since I'm assuming that's what most folks are here for -- lots of attendees this week!)
[20:20] <aschweer> I've assigned the Jira issue & PR to me
[20:21] * pbecker (~rooms@2001:6f8:900:8f1c:7401:7743:bc2e:c899) Quit (Quit: Rooms • iPhone IRC Client • http://www.roomsapp.mobi)
[20:21] <tdonohue> thanks aschweer!
[20:21] * pbecker (~firstname.lastname@example.org) has joined #duraspace
[20:21] <tdonohue> So, next main topic on our agenda is 4.0 (obviously).
[20:22] <tdonohue> the main thing to talk through is of course our pending deadline for New Feature PRs (deadline is next Monday, Oct 7), and starting to get together a plan for reviewing those PRs.
[20:22] <tdonohue> I'd also like to see if the 4.0 RT had anything specific they'd like to discuss today, as it is the last meeting before 4.0 starts to "kick into gear"
[20:23] <tdonohue> I'm noticing mhwood isn't here (from the RT), but hpottinger and abollini are
[20:23] <hpottinger> I'd just like to say, if you've got a big pull request coming, maybe don't wait until Monday to tell us about it... :-)
[20:24] <bollini> all you know that something could come from me... ;-)
[20:24] <hpottinger> https://wiki.duraspace.org/display/DSPACE/DSpace+Release+4.0+Notes
[20:24] <kompewter> [ DSpace Release 4.0 Notes - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DSpace+Release+4.0+Notes
[20:25] <hpottinger> the Release Notes page for 4.0 has a place for you to add incoming new feature notes, if your PR will be "big" it helps to have a writeup on the release notes, it not only lets all of us know what's coming, but it helps us keep on top of informing the community about new features
[20:26] <tdonohue> Also, as noted in the "Timeline & Proceeding" on the 4.0 Release notes, our next 2 developer meetings (Oct 9 & 16) are to be devoted towards PR reviews (of anything that makes it under the deadline), so that we can try to merge as much as possible before we get to the Feature Freeze (Oct 21)
[20:26] <pbecker> I woul be really glad to get https://github.com/DSpace/DSpace/pull/312 into 4.0
[20:26] <kompewter> [ DS-1535: DOI support for dspace-api by tuub · Pull Request #312 · DSpace/DSpace · GitHub ] - https://github.com/DSpace/DSpace/pull/312
[20:27] <pbecker> S/woul/would
[20:27] <bollini> just a note, It will be better if we are able to comment and make suggestion to the PRs before the meeting
[20:27] <helix84> I just wanted to note that I won't have time to work on Metadata for all. It would be terrific if someone else could pick up mdiggory's PR, it mostly just needs to be forward-ported to master.
[20:28] <bollini> the meetings should be reserved to discuss the PR that doesn't have get any feedback but are supported from the original submitter (i.e. he will be present to the meeting)
[20:28] <tdonohue> bollini ++ It'd be best if folks can look at PRs as they come in, to save our meeting time for those needing the most attention/discussion
[20:31] <hpottinger> helix84, so DuraLogBot can have a complete record, can you just mention the PR number of mdiggory's "metadata for all" branch?
[20:32] <hpottinger> well, silly me, it's in the release notes, never mind helix84, for the record, it's PR #12
[20:32] <tdonohue> If the Release Team has any other recommendations on how best to review these PRs as they come in (or how best to organize our next few PR review meetings), I'd recommend you let us all know. I'm essentially leaving these decisions in the hands of the Release Team.
[20:32] <helix84> https://github.com/DSpace/DSpace/pull/12
[20:32] <kompewter> [ Support Metadata On All DSpaceObjects by mdiggory · Pull Request #12 · DSpace/DSpace · GitHub ] - https://github.com/DSpace/DSpace/pull/12
[20:33] <tdonohue> We also can try and "revive" our dspace-release mailing list (which is still there, but not been used much) in order to do more 4.0 planning...and I'd encourage the RT to do so
[20:33] * l_a_p (~email@example.com) Quit (Quit: ChatZilla 0.9.90.1 [Firefox 24.0/20130910160258])
[20:34] <hpottinger> tdonohue: can you define "revive"? :-)
[20:35] <tdonohue> So, RT (hpottinger, bollini, mhwood), if there's a particular order or "set" of PRs you'd like us to review in each of the upcoming meetings, please let us know. If you want we can put specific tickets in the agenda for each week, but I'm leaving that up to you
[20:35] <tdonohue> hpottinger: mostly I just mean it's been a bit "quiet" on dspace-release... We can start doing more stuff there, like suggest PRs that need more eyes (before meetings), etc
[20:35] * helix84 cracks a whip
[20:36] <hpottinger> sounds like a good plan, anyone who has strong feelings about particular incoming PRs, dspace-release is the best place to express them
[20:37] <tdonohue> hpottinger: I didn't mean to imply that it's bad that it's been "quiet", though :) I just meant that as the 4.0 Release starts ramping up, we should remember that's a good place to collaborate ;)
[20:37] <bollini> we should make a list of the acceptable PR on monday send a mail to the tech/devel/release list asking to all interested in to sign on a wiki page for the two dedicated irc meetings
[20:38] <hpottinger> no offense taken, I just wanted to be sure what we were discussing
[20:38] <tdonohue> bollini: that'd be great if the RT wanted to create a quick PR list for us to work from
[20:39] <helix84> bollini: the important thing is to sort them by priority (likeliness of getting them merged)
[20:39] <bollini> I will prefer to spent more time making review but if noelse is available I can make the wiki page
[20:40] <hpottinger> wiki is OK, but mail list would be faster
[20:40] <tdonohue> (plus, having a list of those PRs we need to most look at will help us to better "filter out" other PRs that we can ignore for now...e.g. PRs relating to just bug fixes, or ones that are still "in progress" work that are not ready for acceptance)
[20:41] <hpottinger> oh, I wonder if we can ask the "feature owners" to make this list for us?
[20:43] <tdonohue> hpottinger: we could, but it might be 'incomplete' (if some 'owners' are not responsive enough). I'm noticing we have 49 currently "open" PRs. My big question is are we going to 're-review' them all in light of 4.0, or is there a way to "streamline" our list.
[20:46] <tdonohue> It seems like there are many (in that list of 49) which have "stalled"...there's recent comments asking for updates/changes that were never answered. Those that are "stalled" it seems like would not be applicable for 4.0, unless someone decided to adopt the work to move it forward.
[20:47] <bollini> Ok, someone from RT (maybe me...) can prepare for monday a categorized list of these PR
[20:47] <tdonohue> so, it's almost like we have three categories: (1) 4.0 Feature PRs needing review, (2) Bug-fix PRs (also needing review, but can be reviewed later), and (3) Stalled PRs (won't be accepted unless someone wants to step forward and adopt it / restart it)
[20:47] <tdonohue> sounds good, bollini
[20:48] <hpottinger> bollini, you may want to do that list prep on Tuesday, since the deadline is Monday
[20:49] <tdonohue> So, do we want to open up the floor here to see if anyone is working on "last minute" PRs we should anticipate by Monday?
[20:49] <bollini> tdonohue: yes, also making distinction between green button available or conflict for PR in category 1
[20:49] <hpottinger> tdonohue++ and bollini++
[20:51] <tdonohue> One PR-specific question I had... Has anyone been working with or talking with Richard Jones about his SWORDv2 fixes? (PR#229 : https://github.com/DSpace/DSpace/pull/229) I recall him saying he needed some "git" expertise to get his PR rebased/cleaned up.
[20:52] <kstamatis> We are working on a new version of BTE (new core + new data loaders) and a UI to call its function within it (for batch importing from various bibliographic formats)
[20:52] <kstamatis> We have seen the similar work by bollini, we want to give it a try
[20:53] <robint> tdonohue: I will give Richard a ping
[20:53] <bollini> kstamatis: very good news! we can try to merge the two approach
[20:53] <tdonohue> Perhaps (regarding Richard Jones' PR#229) I should have asked, is anyone willing to reach out to Richard to see if he still needs help :)
[20:53] * pbecker (~firstname.lastname@example.org) Quit (Quit: Rooms • iPhone IRC Client • http://www.roomsapp.mobi)
[20:53] * pbecker (~email@example.com) has joined #duraspace
[20:53] <tdonohue> oh, thanks, robint. Just wanted to make sure we got Richard's fixes in :)
[20:54] <kstamatis> bollini: we can skype tommorow to see details
[20:55] <bollini> kstamatis: yes
[20:55] <tdonohue> Another 4.0 PR question.. PeterDietz, any chance you'll be able to have an "early version" Jersey REST API PR ready in time (which rumor has it you are working towards)? Not wanting to put you on the spot, more just curious if there's enough time left :)
[20:57] <bollini> I'm also interested in known if anyone is planning to ask for a small extension...
[20:57] <tdonohue> PeterDietz: or if you need want help or a small extension (as bollini mentions)
[21:00] <tdonohue> Any other "possible PRs" we should expect from anyone? I'm noticing we've got a *lot* of attendees today (which is awesome) but not a ton of discussion. Is everyone just wanting to listen in on "what's possibly in 4.0"? :)
[21:00] <robint> Erm, yes :)
[21:01] <tdonohue> well, at least you own up to it, robint ;) I figured some were in that camp of just wanting to lurk/listen
[21:01] <aschweer> I've got a handful of tiny bugfix-style changes (against 1.8.2), I'll need to check if they're still relevant for 4.0. I'm hoping to get to that before Monday
[21:02] <hpottinger> robint, is that "yes" as in "yes, we have a PR we're preparing?" or "yes, I'm lurking?"
[21:02] * pbecker (~firstname.lastname@example.org) Quit (Quit: Rooms • iPhone IRC Client • http://www.roomsapp.mobi)
[21:02] * pbecker (~rooms@2001:6f8:900:8f1c:7401:7743:bc2e:c899) has joined #duraspace
[21:03] <helix84> aschweer: bug fixes can go in even after Monday
[21:03] <aschweer> helix84: ah good, I had lost track of the schedule a bit
[21:04] <helix84> aschweer: well, bug fixes are welcome at ANY time (except the day when the RT actually wraps up a release)
[21:04] <hpottinger> I'd let a bug fix in even on release day
[21:04] <pbecker> As I mentioned before, I would be glad to get the Doi stuff into 4.0. I filed the PR today. DS-1535.
[21:04] <kompewter> [ https://jira.duraspace.org/browse/DS-1535 ] - [#DS-1535] DOI support for dspace-api - DuraSpace JIRA
[21:04] <PeterDietz> hi. pulled away for a meeting
[21:05] <PeterDietz> To give people something real to test out, any hints on mechanics of that?
[21:05] <helix84> PeterDietz: demo.dspace.org (possibly during testathon)?
[21:05] <PeterDietz> ... PR / merge jersey into upstream dev branch, and install on demo
[21:05] <PeterDietz> ...or just checkout demo to my feature branch...
[21:06] <tdonohue> realizing we're now a bit "overtime" here...which means I probably shouldn't delve into other agenda topics (but we can continue 4.0 topics as long as folks want to hang around). There was one final topic (about "what belongs in build.properties"), but I'll email dspace-devel about that to get the discussion started there.
[21:06] <robint> hpottinger: just lurking :)
[21:07] <hpottinger> PeterDietz, I could try to get a branch of vagrant-dspace to demo your jersey REST
[21:07] <PeterDietz> Just checking the dates.. So make the PR before Oct 07.. I could make it any time, but I'm feverishly working and improving it.. Several commits a day for the past week or so
[21:07] <bollini> pbecker: I will try to take a look to your work on DOI... can you hightlight some charateristics? are there any relationship with the work done on Dryad?
[21:08] <helix84> tdonohue: Any news regarding the possibility of DuraSpace hosting more than one demo site? You said it's possible now that your cloud thing is ready.
[21:08] <robint> Lurking over, cheers all!
[21:08] <pbecker> I talked to ryan from datadryad and I want to write him a mail in the next days. But I was not able to take code from them.
[21:09] * robint (5eaf588c@gateway/web/freenode/ip.22.214.171.124) Quit (Quit: Page closed)
[21:09] <PeterDietz> so.. could I treat demo.dspace.org as sort of project space... i.e. /jspui -> 4.x jspui, /jersey -> peterdietz/jersey
[21:09] <pbecker> I tried to document the idea behind the pr in the wiki. The article is linked in jira ticket.
[21:09] <PeterDietz> any advice helpful, I've usually used distinct servers for distinct feature sets
[21:09] <tdonohue> PeterDietz: yea, a REST API PR would need to be made before Oct 7. It can be improved *after that* obviously, though it really should stabilize & be merged before we get to Feature Freeze (Oct 21) deadline.
[21:09] <helix84> PeterDietz: I don't think there's enough memory there to run too many webapps
[21:10] <bollini> pbecker: ok, I will try to read as much as possible from your pr. I want to suggest you to get feedback from the dryad people
[21:10] <PeterDietz> maybe I can talk to my local sysadmin and spin up an OSU VM
[21:10] <bollini> pbecker: they have experience in use DOI with dspace so your PR should work in their use case if possible
[21:10] <helix84> bollini: mhwood also looked at pbecker's DOI work and even added the other big DOI provider implementation (different API)
[21:10] <pbecker> bollini: Thank you. I'll write ryan and ask for his comment.
[21:11] <bollini> pbecker: your implementation is about datacite right?
[21:11] <pbecker> helix84: I was thinking about merging both. Didn't had the time yet.
[21:12] <helix84> pbecker: this is your chance to ask for a deadline extension ;)
[21:13] <bollini> I'm sorry I need to leave now... keep in touch
[21:13] * bollini (~email@example.com) Quit (Quit: ChatZilla 0.9.90.1 [Firefox 24.0/20130910160258])
[21:13] <pbecker> bollini: almost. Different datacite members uses different APIs. My code uses the DataCite API directly. EZID f.e. is a DataCite member but they have their own API.
[21:13] <tdonohue> PeterDietz, if you really need a place to put your REST API for demoing, you could just replace the HedTek REST API (currently running there) with your Jersey REST API
[21:14] <pbecker> helix84: thanks, I'm fine with the pull request. There is always something that still can be done. I think it won't be my last PR. ;-)
[21:15] <tdonohue> PeterDietz & helix84 - If we need a bigger demo.dspace.org server (more memory), we might also be able to do that... I'm just not sure when I'll be able to get to that (my plate is very full right now)
[21:16] <helix84> tdonohue: on a different note, I also wanted to ask you if you had the chance to add embargo support to AIP as you planned (for dspace-replicate, I think)
[21:17] <aschweer> gotta go, bye all
[21:17] * aschweer (~firstname.lastname@example.org) Quit (Quit: leaving)
[21:18] <tdonohue> helix84: no, I have not. I'm not going to have any significant time for 4.0 development, unfortunately. My time is currently split between DSpaceDirect and DSpace, which vastly limits my actual programming time. Most of what I'm able to contribute for 4.0 has been in vagrant-dspace, as it was related to stuff I was doing for DSpaceDirect
[21:18] <tdonohue> (and yea, I know 'vagrant-dspace' isn't directly related to 4.0, but it might be really useful for Testathon)
[21:18] <pbecker> Does anyone know if Item Versioning Support and AIP will work well together one day?
[21:19] <tdonohue> pbecker: I think we'd all love for it to work better. Just needs a volunteer developer. Currently AIPs only are able to capture the *latest* version of an Item.
[21:20] <helix84> pbecker: I see noone from @mire here today (the contributor of both features), but I understand their position is that their contract on these features has been completed and they don't have immediate plans to work on it.
[21:21] <pbecker> helix84: didn't know that. I hoped they were working on it...
[21:21] <hpottinger> so, helix84 brings up a good point, if there's a feature you want changed, contacting the original submitter and collaborating or otherwise working together with them is one very good way to ensure the feature works the way you wish
[21:22] <tdonohue> To clarify, AIP support was developed by myself (DuraSpace), with some support from Richard Rodgers/MIT. Item Versioning is still a "beta" feature, and it was developed by @mire (and when they created it, they did not update AIPs to support Item Versioning, which is why AIPs only capture the latest version of an item).
[21:23] <helix84> yes, I think our major problem as a community at this time is that we need to test and review each other's new code much more and not just leave it up to commiters
[21:23] <helix84> tdonohue: sorry about the misattribution
[21:24] <tdonohue> DS-1374
[21:24] <kompewter> [ https://jira.duraspace.org/browse/DS-1374 ] - [#DS-1374] AIP Backup & Restore functionality does NOT backup/restore past versions of Items - DuraSpace JIRA
[21:24] <helix84> what I meant was that @mire contributed versioning and embargo (not AIP)
[21:25] <tdonohue> helix84: oh, yea, that's true. @mire did contribute versioning & *advanced* embargo (the latest embargo stuff)
[21:25] <helix84> both those features have rough edges in relation to AIP
[21:25] <tdonohue> yes, unfortunately that is the case
[21:26] <tdonohue> AIP stuff was built before those features came in, and unfortunately the AIP work has not yet been updated to fully support those features
[21:26] <helix84> but as both need a change in the actual AIP format, I think DuraSpace would have the most important voice in proposing how to do that
[21:27] * pbecker (~rooms@2001:6f8:900:8f1c:7401:7743:bc2e:c899) Quit (Quit: Rooms • iPhone IRC Client • http://www.roomsapp.mobi)
[21:27] * pbecker (~rooms@2001:6f8:900:8f1c:7401:7743:bc2e:c899) has joined #duraspace
[21:27] * kstamatis (2ebe5dfb@gateway/web/freenode/ip.126.96.36.199) has left #duraspace
[21:28] <tdonohue> helix84: I'd be glad to help brainstorm ideas with someone on how to fix/change/update the AIP format. But, not sure I can do any java development on it. The AIP format history was that I created it based on some old (now obsolete) AIP work that MIT initially started many years ago now.
[21:29] <helix84> tdonohue: if you could draft what the changes in format should look like, I think that would be a start (and not much work)
[21:32] <tdonohue> helix84: again, not sure when I'd get to that, as AIPs are not something I'm spending a lot of time with these days. I'm hoping to get back to it at some point, but not sure if it'd be in a month or a year :)
[21:33] <tdonohue> so, if we want/need something more immediately, I'd suggest we look towards finding others to help chip in on AIPs. Again, I'd be glad to help consult with whomever, but AIPs are not my top priority these days, unfortunately.
[21:34] <pbecker> I'm quite interessted in versioning and AIP, but there are other things more urgent for us I'll work on in the next few month.
[21:36] * PeterDietz (~email@example.com) Quit (Ping timeout: 246 seconds)
[21:36] <tdonohue> pbecker. If you ever get back to looking at AIPs, I have some basic notes in DS-1374 and DS-1382 about versioning + AIPs. But, I didn't get much further than those notes. Still, be glad to offer suggestions/review code if you get back to it.
[21:36] <kompewter> [ https://jira.duraspace.org/browse/DS-1374 ] - [#DS-1374] AIP Backup & Restore functionality does NOT backup/restore past versions of Items - DuraSpace JIRA
[21:36] <kompewter> [ https://jira.duraspace.org/browse/DS-1382 ] - [#DS-1382] AIP Backup & Restore functionality should not duplicate unchanged files across Item Versions - DuraSpace JIRA
[21:37] * PeterDietz (~firstname.lastname@example.org) has joined #duraspace
[21:38] <pbecker> tdonohue: thanks. First thing I normally do is a quick search in jira, so I'll find this whenever I'll get back to it.
[21:38] <tdonohue> pbecker: yep, makes sense
[21:38] <pbecker> Have to leave no... Bye!
[21:38] <pbecker> s/no/now
[21:38] <kompewter> pbecker meant to say: Have to leave now... Bye!
[21:38] * pbecker (~rooms@2001:6f8:900:8f1c:7401:7743:bc2e:c899) has left #duraspace
[21:40] * hpottinger (~email@example.com) has left #duraspace
[21:42] <helix84> I tried to find a ticket on simple embargo and AIP, but I couldn't. Similarly, resourcepolicy start and end date is missing from METS - this is a simple addition Terry Brady has been working on and might be ready by Monday.
[21:43] <helix84> good night
[21:43] * helix84 (~firstname.lastname@example.org) has left #duraspace
[22:07] * PeterDietz (~email@example.com) Quit (Remote host closed the connection)
[22:14] * tdonohue (~firstname.lastname@example.org) has left #duraspace
These logs were automatically created by DuraLogBot on irc.freenode.net using the Java IRC LogBot.