[
http://jira.dspace.org/jira/browse/DS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11695#action_11695
]
Robin Taylor commented on DS-619:
---------------------------------
A couple of suggestions, either...
Look for and delete all old exports whenever anyone does an export ie dont just
delete the old exports for the user doing the current export
or...
Replace the org.dspace.app.itemexport.* directory as defined in dspace.cfg with
the local operating system temp directory retrieved with
System.getProperty("java.io.tmpdir"), and leave the operating system to tidy up
old files.
Anyone got any thoughts on this?
> Item exports not deleted on deletion of eperson
> -----------------------------------------------
>
> Key: DS-619
> URL: http://jira.dspace.org/jira/browse/DS-619
> Project: DSpace 1.x
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.6.0, 1.6.1, 1.6.2
> Reporter: Claudia Jürgen
> Assignee: Robin Taylor
> Priority: Minor
> Attachments: DS-619.patch
>
>
> An eperson's item exports are not deleted when the eperson is deleted. This
> results in orphaned entries in
> [dspace.dir]/exports/download/[EpersonID] as the exports are only deleted if
> an eperson creates a new export and got old exports which exceed the timespan
> configured.
--
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
