[
http://jira.dspace.org/jira/browse/DS-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11700#action_11700
]
Tim Donohue commented on DS-621:
--------------------------------
This issue was discussed in Developer Meeting on Sept 22, 2010:
[20:14] <tdonohue> Export cleanup : http://jira.dspace.org/jira/browse/DS-621
[20:14] <tdonohue> hmm.. DS-621 is related to DS-619 (though they aren't linked
in JIRA right now)
[20:15] <kshepherd> same issue basically..
[20:15] <tdonohue> thoughts? Should we really be cleaning up exports via a cron
job (thus making DS-619 obsolete before it's even committed)?
[20:15] <mhwood> Yes
[20:15] <robint> Yes, I wish I hadn't volunteered earlier now, doh ! assign to
me.
[20:15] <mhwood> Oops, yes they seem related.
[20:16] <grahamtriggs> 619 specifically cleans up when Eperson is removed, but
621 is the general - 'do we really want this stuff hanging around even when the
eperson remans'
[20:16] <tdonohue> Right, but if we implement DS-621, we don't need DS-619,
correct?
[20:16] <mhwood> OTOH if 621 is done by cron then it can handle 619 as well?
[20:17] <tdonohue> robint -- are you volunteering to implement DS-621 instead
of DS-619? (just want to clarify)
[20:17] <grahamtriggs> depends... the fix for 621 may depend on the eperson
still existing.
[20:17] <mdiggory> why not just cache the exports in the temp directory and let
a steriotypical tmp cleanup manage them?
[20:17] <robint> I'll review qnd come back with a suggestion. oIs that ok ?
[20:18] <robint> s/oIs/is
[20:18] <grahamtriggs> don't we need to guarantee that the exports will be
available for a certain period?
[20:18] <tdonohue> robint -- sounds good to me
[20:18] <tdonohue> grahamtriggs -- yes, but we probably should just let
institutions decide on that period, and schedule their cron job appropriately
[20:18] <robint> mdiggory: Thats topical for me anyway as that is what Sword
does.
[20:19] <tdonohue> ok -- assign DS-621 to robint for review/suggestions. This
may or may not make DS-619 unnecessary
> Export cleanup
> --------------
>
> Key: DS-621
> URL: http://jira.dspace.org/jira/browse/DS-621
> Project: DSpace 1.x
> Issue Type: Improvement
> Components: DSpace API, JSPUI, XMLUI
> Reporter: Claudia Jürgen
> Assignee: Robin Taylor
> Priority: Minor
>
> The exports of an eperson are only deleted if the eperson exports another
> item and the existing exports exceed the lifespan configured. This is a bit
> clumsy as exports might thus linger forever.
> Exports should be cleaned up via a cron job.
> Furthermore the lifespan of an export should be indicated in the My DSpace
> and the user should be able to delete his own exports.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
