Nudging this message, hoping to get a response.
Related to the deleted harvest, we have a range of orphan identifiers. We
believe these were created from the first harvest (entire test instance)
and that they were orphaned when I initiated the collection delete before
the harvest had finished.
We wonder if the best thing might be to manually remove them from the
database, but that doesn't help with the artifact collection described
below.
Any feedback is appreciated!
Nathan
---------- Forwarded message ----------
From: Nathan Tallman <ntall...@gmail.com>
Date: Wed, Oct 8, 2014 at 1:01 PM
Subject: Artifact after Deleting Harvested Collection
To: "<dspace-tech@lists.sourceforge.net>" <dspace-tech@lists.sourceforge.net
>
This morning, we were doing some tests on our Dspace (1.8.2) instance,
following a system change. The testing involved an OAI-ORE harvest from our
test instance. Initially for this test, I neglected to click on the radio
box for a specific set and Dspace tried to harvest our entire
test-instance. After realizing my mistake, I was able to edit the settings
for a specific set and clicked "reset and reimport." This appeared to be
successful: records that had just been imported went away, the new subset
appeared. After this confirmation, I initiated a delete of the collection,
since this was just a test.
Oddly, the items seem to have deleted, but the test collection still
appears in the sub-community list and the overall communities and
collections page. However, wherever it appears, it only links to the page
it's on. You can see what I mean here:
https://drc.libraries.uc.edu/handle/2374.UC/730895 (see the "Test Harvest"
collection. In other words, we can't tell what the "Test Harvest"
collection handle really is/was, because it always links to the identifier
for the page it appears on.
I can create new collections and submit new records; the new handles
function properly.
Does anyone have experience with this type of issue or have any feedback to
offer? It's perplexing and we're wondering if a re-index will rid us of
this artifact.
Thanks,
Nathan
----
Nathan Tallman
Digital Content Strategist
University of Cincinnati Libraries
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
