Deleting a collection....doesn't. #50
Milestone
Comments
|
That solr bit might be a red herring. We should make another ticket to move to osgi fcrepo-camel-toolbox and not install the solr indexer since we get that for free with Drupal. The not getting deleted from Fedora bit is still extremely relevant, though! |
|
Yeah I just noted it was looking for Solr on the wrong port (localhost:8983). So that is not relevant. |
|
Yeah, that's the camel tool box. We should probably custom compile that with the proper configuration. |
|
In case someone gets around to this before me, I recently did it for fcrepo4-vagrant in preperation for HydraConnect 2015. |
|
...you already have karaf installed, so I'll work to add the fcrepo-camel-toolbox.script. |
|
I think we just need to set the |
|
...or not use Solr, because we're using Drupal's Solr 😄 |
|
I'd just switch over to using karaf and then not install the indexing-solr feature. |
|
Yeah but the karaf is easier, I've got a PR for the fcrepo-webapp-plus. You can even set the path once it's running and it just works. I may be coming around to OSGi. |
|
I just tested this out on the #47 branch, and it deleted fine. fcrepo web interface:
catalina.out karaf: |
|
@dmoses is going to test, and confirm whether or not this is still an issue. |
|
I created a collection object in Drupal. I then Edit > Delete the Collection in Drupal. When I viewed it on Fedora I get this message: |
|
@dmoses, other of the particularities of LDP + Fedora4. Fedora makes tombstones for deleted resources, when deleting, resources get wiped out, but the resource path persists (means you can not reuse the same path), so it's expected behaviour. @daniel-dgi, do you know if there was a workaround at fedora level for this? |
|
I've deleted the tombstones with curl curl -X DELETE http://localhost:8080/fcrepo/rest/mycollection deletes the collection but then you get the tombstone, so next do curl -X DELETE http://localhost:8080/fcrepo/rest/mycollection/fcr:tombstone then you can use that name again to add |
|
I like the idea of tombstone data ... I think it is the UUID that can't be reused ... may be wrong though? There may be good reasons from a preservation perspective that you want to maintain tombstone info. |
|
@dmoses, we are using UUID, but for fedora, the unique id for a resource is the path. If they match (partially) depends on the pid minter used and/or the way we are creating our path. I also like having it, you are true, very useful in production, but sometimes trouble when you are testing/developing. By the way @bsw2, thanks! |
|
Tombstones are the intended behaviour. |
|
This is the old 7.x-2.x architecture. Microservices is different and does delete. |
|
@whikloj close/won't fix? How's that sound? |
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Created a collection via the Drupal interface.
(It did have the title "Archives & Special Collections")
When I went to delete it, it is removed from Drupal. But this is what I saw in the catalina.out logs.
It is not removed from Fedora.
The text was updated successfully, but these errors were encountered: