[
http://jira.dspace.org/jira/browse/DS-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=11474#action_11474
]
Pere Villega commented on DS-532:
-
Hi,
as this has become a GSOC project, maybe we can close this
LDAP users with no mail field can't autoregister
Key: DS-586
URL: http://jira.dspace.org/jira/browse/DS-586
Project: DSpace 1.x
Issue Type: Bug
Components: DSpace API
Affects
add the capability to indicate a withdraw reason to an item ( tombstone )
-
Key: DS-587
URL: http://jira.dspace.org/jira/browse/DS-587
Project: DSpace 1.x
Issue Type:
[
http://jira.dspace.org/jira/browse/DS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jose Blanco updated DS-587:
---
Attachment: tombstone.jsp
embargo.jsp
confirm-withdraw-item.jsp
I've included here
Most DSpace objects are created within the repository all at once.
Items appear to be unique in that they are created, exist for a while
within a workflow, and then enter the repository proper. There
doesn't seem to be an Event type for the transition from workflow to
repository. CREATE happens
Quick question:
We had a user delete things he should not have. We have been able to
restore the filesystem stuff from backups. Unfortunately, the database
backups have been lost. All we really need is the content files. Is
there a way to rebuild the content files from just using what is on
Others should provide some clarification on this, but typically deletions are
not hard deletes but soft, in that there is a deletion flag that a cleanup
process operates on occasionally. Perhaps the database still contains the
items, and you can revert the deletion by modifying the correct
I would look in the database table item. It has a field called
item.in_archive. Typically when an item gets deleted it sets
item.in_archive to FALSE
So from the DB, you could look for all of the deleted items. So use your
favorite SQL query tool (perhaps pgAdmin3 if your DB is postgres)
SELECT *
On May 28, 2010, at 11:19 AM, Mark H. Wood wrote:
On Fri, May 28, 2010 at 09:56:51AM -0700, Mark Diggory wrote:
Not only this, but with the work I am planing for discovery, we need events
for all the workflow stages and state changes (withdrawn, submitted, etc)
...
Hmmm. I was also
Thank you for the info so far: The problem with getting technical info
from a user :-(
OK. The user did not delete the individual items, he actually deleted
the COMMUNITY. I dont see the data for the record in the community
table. Are we SOL?
Again, thank you all for the suggestions and
Jeff,
Unfortunately, There is significantly more than just the Community table that
is effected here. You actually loose the Item, Metadata and Bundle table
entries that were present. All that is left is the Bitstream Table with the
flag that the Bitstream has been deleted. You would need to
[
http://jira.dspace.org/jira/browse/DS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=11476#action_11476
]
Peter Dietz commented on DS-570:
I have been able to implement something like that in the JSPUI, however
12 matches
Mail list logo
