I think that the original reason for this was sort of security via obfuscation - the developers didn't want users to be able to guess the paths for draft descriptions that might have cached XML and thereby access the metadata. However, with development this could be changed - we could improve AtoM's overall security for paths like this, add an option to ensure that draft descriptions don't get cached XML, etc. and then use the slugs (possibly with a format appended, e.g. slug-ead and slug-dc for example).
However, in the meantime, I did find an older developer's script that can be used to return the path to a cached XML when given the related information object (i.e. description) slug. See:
A couple of notes on this:
First, this was created in 2017, and I have NOT tested it yet to make sure it still works!
Second, this is currently set up to return the path to the EAD XML. However, I think if you changed the ead parameters on lines 32 and 33, it should work for DC XML.
You can run this script using the generic tools:run task. The process would look something like this:
- Go to the following URL, and save the file as dc_cache_filepaths.php
- Remember to change the ead parameters in lines 32 and 33 to dc
- Place this file somewhere accessible to AtoM - the root AtoM directory would be fine.
- Use the tools:run command to execute the script:
- php symfony tools:run dc_cache_filepaths.php
- Remember, if you didn't put the script in the root directory, then you'll need to include the file path to the PHP file you want to run.
- The script will prompt you for the slug - enter it, and the script should return the file path of any associated cached xml files.