If you've followed our instructions for setting up the AtoM Vagrant box, then there shouldn't be any restrictions on uploads or downloads, imports or exports.
When everything is working, you should be able to export archival descriptions in CSV format using the Clipboard in the user interface - see:
You can also export description search/browse results in CSV format from the user interface:
There are also command-line export options described here:
One unfortunate catch is that we currently do not have any export options for accession records! I will return to that later.
First, let's see if we can sort out the 500 error that you are encountering. The most likely cause is that the job scheduler needs to be restarted - it performs the Clipboard and Search/Browse result exports via the user interface asynchronously in the background as a job. Occasionally, it seems to require a restart after periods of inactivity. See:
You can try restarting it in the AtoM vagrant box with the following, run from the root AtoM directory:
- sudo systemctl restart atom-worker
You may want to clear the application cache and restart PHP-FPM as well, for good measure - however, be aware that doing so may clear your browser session, meaning you may be logged out, and any records currently pinned to the clipboard might be lost. Try it without first, but here are the commands:
- php symfony cc
- sudo systemctl restart php7.0-fpm
If that doesn't resolve the issue, then we'll want to learn more about the exact nature of the error, as captured in the webserver error logs. You can access these with the following command:
- sudo tail -f /var/log/nginx/error.log
(PS you can press CTRL or CMD+C to exit out of the error log)
Please feel free to share any message you find in the error log relevant to this issue, and I can provide further suggestions based on it.
I would also suggest you look at the new Troubleshooting
documentation page - it contains a wealth of information on common solutions to reoccurring issues.
Regarding the accessions: if you are a developer who is confident working with SQL, you could try to extract them directly from the AtoM MySQL database. I don't have a query handy that will magically do that for you, but I can point you in the right direction with some resources if desired.