Hi Patrick,
Thanks for clarifying.
That does sound like incorrect behavior - the warnings should not display if all the date fields are filled. In any case, if you're just evaiuating the software, the good news is:
- I can't reproduce this issue creating a test description on our public demo site
- In any case, the warning you are describing is ONLY ever shown to logged in users, and not to public users.
Regarding 1:
Our public demo site is currently running v2.7.3 as well (it looks like it hasn't yet been updated to the latest 2.8.1 release), but I was unable to reproduce the issue there. Hopefully this suggests that it is just an issue currently affecting your local Vagrant instance, and not a bug in the application. Would you like to try to reproduce it there as well - login credentials are on the homepage; the site resets hourly so if you or someone else makes a breaking change don't worry, it will get wiped away soon enough. Also note that for security purposes some functionality (like uploads of any kind) is disabled in the public demo:
AtoM was originally built around the ICA content standards (e.g. ISAD(G), ISAAR-CPF, ISDF, ISDIAH) and one of its early project goals was to make it easier for smaller or under-resourced archival organizations to describe their holdings in a standards-based way and make them available online. Despite this, AtoM is purposefully designed as a very permissive application, and doesn't actually enforce any of the standards-based content validation it performs on save. By this I mean: you can actually open a blank archival description template (via Add > Archival Description) and immediately save it with no data at all added - AtoM will let you create an entirely blank description.
Despite this, the warnings you have noted are taken from the relevant content standard (i.e. whichever description template you are using), to help users who want to follow the intended guidelines or rules for that particular standard. ISAD(g) marks just a small handful of fields as mandatory - if these are left blank, then authenticated users (i.e. typically staff users) will be shown these warnings on the view page of the relevant description. However, there are many times when leaving such fields blank is fine or even intentional (for example, most people don't have the time to describe everything in detail down to the item level).
That said, I think it's likely that if we go through the process of upgrading your local Vagrant instance, we might resolve the issue. Doing so will require running a number of command-line tasks. Is this something you'd like me to provide some guidance on? And if yes - do you have data in your Vagrant test instance that you want to preserve?
Cheers,