Collection record displays incorrectly and cannot be edited/deleted

[Francisco Bosch Puche]

Dear colleagues,

Hello from the Griffith Institute Archive, University of Oxford. 

We have encountered an issue with a specific collection record in our catalogue and would appreciate any advice on how to diagnose or resolve it.

The collection in question is:

https://archive.griffith.ox.ac.uk/index.php/clackson-collection

Unlike all other collections in the catalogue, this record does not display correctly. When logged in, it is possible to make some edits, but it is not possible to update the slug, delete the record, or move it to draft status. We have only recently noticed this issue, so unfortunately we do not know how long the record has been displaying in this way.

The collection has many descendant records, which can be viewed here:

https://archive.griffith.ox.ac.uk/index.php/clackson-1

From this page, the full hierarchy is visible. However, it is not possible to navigate back to the parent collection record from the tree view, nor does the collection record itself provide access to the hierarchy.

This is the only collection in the catalogue (out of approximately 170 collections) that behaves in this way.

We have considered creating a new collection and moving all descendant records to it. However, because the current collection cannot be deleted or unpublished, users would ultimately see two collections, which is not an ideal solution.

We are currently running AtoM version 2.10.1 (build 197).

Has anyone encountered a similar issue, or can you suggest how we might investigate and fix this record?

Many thanks in advance.

Best wishes,

Francisco Bosch-Puche
GI Archive Curator

P.S. This is my first time posting to the group, as a former colleague would usually have handled these matters. Please forgive me if I have not followed the usual procedure or if my description of the issue is unclear.

[Alberto Pereira]

Hi Francisco,

This specific page (https://archive.griffith.ox.ac.uk/index.php/clackson-collection) is throwing an internal error (500). It's possible to view that it is happening in the browser, but not what the error is exactly.

To know exactly what's going on, you'll need to check with the IT admin who has access to the server to verify the logs. From there, you'll have more information with which to work. I suspect a broken hierarchy somewhere, and maybe rebuilding the nested set is enough (https://www.accesstomemory.org/en/docs/2.10/admin-manual/maintenance/cli-tools/#rebuild-the-nested-set), but I can't be sure.

good luck!

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/1bfc177c-f58e-4054-b65c-668e04aaf96cn%40googlegroups.com.

[Clara Rosales]

Hi Francisco,
I think the problem stems from the "Rights" field.
Run this query on your database:

SELECT s2.slug
FROM relation r
INNER JOIN slug s1 ON r.subject_id = s1.object_id
INNER JOIN slug s2 ON r.object_id = s2.object_id
WHERE s1.slug = 'clackson-collection'
  AND r.type_id = 168;

It will return a string of numbers and letters, like a1b2-3cc3-ddd8.
Delete the "Rights" field associated with the 'clackson-collection' description at: https://archive.griffith.ox.ac.uk/index.php/a1b2-3cc3-ddd8/right/delete
If the error lies there, the record will display correctly after deletion.
Greetings!

--