The Embedded Collecting Event option and the three remote preferences CO_CREATE_COA, CO_CREATE_DET & CO_CREATE_PREP proved very useful for easing up and securing new CO entry. Number of clicks is decreased and mandatory fields are clearly identified.
A Collecting Event does not make sense without a Collector in CAY herbarium. When I set up the CO_CREATE preps, my colleagues immediately asked whether a new Collector could be automatically created as well, since it is mandatory in our data entry process.
Can one automatically creates a new Collector upon CE creation ?
I’m also wondering why you decided to implement COA, DET & PRE creation through Remote Preferences ? (genuine question) Have you thought of a generalized approach in viewdef resources, with for instance and XML attribute that would control the underlying resource creation ?
onDataEntry : create the underlying object on new data entry only
ifEmpty : create the underlying object on new data entry or on data edition if empty
?
Feel free to split the last bit to a separate thread “Generalizing automatic object creation on Data Entry” if the thought interferes with my 1st question on collector creation.
Thank you so much for your message and for your valuable feedback on the automatic creation of a new Collector upon CE creation. I’ve added a GitHub feature request for this:
We appreciate your suggestion!
I agree that a generalized approach would be best, and I’ll pass that along to our development team as well!