Essentially asking for events to function more similarly to agents and linked resources/accessions. I can see how this could be useful, but the current workflow doesn’t appear to be significantly more arduous than an adjusted one. If passed, low priority. If not passed, I would recommend changing the label “Add event” to “Create event” to better indicate the intended function.
Since this is causing validation issues, it seems good to pass. The order is well-defined, so shouldn’t be overly difficult to add to the transformation. It sounds like forcing the order in ASpace instead (i.e. not allowing a form subdivision to be added after a chrono one) would cause issues with legacy data.
Requested clarification and a use case. No response yet.
Documentation seems pretty intentional that Coll. Management records should only be at the collection level. Management information for specific objects can be recorded in the collection level note - a processing plan can be entered in text or a link to local document. One an also make use of the “Repository Processing Note” in each object. The assessments module could also be used at the object level to track specific processing needs and priorities. Recommend not passing.