You can also check the status of the job in the user interface, via the Jobs page (Manage > Jobs):
If it doesn't work, there may be a problem with the job scheduler. I would first confirm with your IT support that the job scheduler and its requirements have been installed correctly, as per the instructions found here:
You can also use the following command-line tasks to check the status of the atom-worker, and restart it if necessary (details included in the documentation link above):
Next - if you have the finding aid options set to generate finding aids as a public user, I would suggest that you try changing this setting to "No," and check to see if the options show up on the target description. If so, there might be some problem with the publication status - perhaps you tried to publish a large hierarchy all at once via the user interface, and the operation timed out before all records were published, leaving some corrupt data or no publication status.
If this turns out to be the case, you might try using the CLI task to publish the description again. See:
You might also want to clear the application cache and repopulate the search index - it's unlikely but possible that the record is in draft mode, but the cache is presenting it as published.
Note that if this does end up being the case, there are several improvements in the upcoming 2.3 release that should prevent you from encountering this exact issue in the future. First, we have changed the Publication status update to use the job scheduler - so it will run asynchronously in the background, and will not time out via the browser during large requests. You'll now find the Publication status update options in the More button, instead of in the Admin area of the description's edit page in 2.3. Documentation on this feature can be found here. Second, we have introduced database transactions in the backend - so if you perform an operation that times out via the browser, AtoM will automatically roll the database back to the last well-known state before the action, instead of terminating with corrupted data, which can lead to all kinds of difficult to diagnose issues that sometimes take time to appear. Note that the 2.4 release will also vastly improve the Generate finding aid workflow (less confusing status messages, easier workflow, option to delete existing finding aids, a more obvious/visible button for end users to download the finding aid, and options to upload your own finding aids instead of generating one from the description).
I'll leave it there for now - we can start with those initial troubleshooting steps to see if they help us better isolate what and where the issue might be. Let me know what you find, and if you're still experiencing issues, I will see if the developers have any further suggestions.
Cheers,
--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/cfa93521-c535-416a-aa9e-18857cc35540%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.