It might be possible for us to change this in the future, but it will certainly require development - and I think, to prevent constant timeouts, we'd want to do it once EAD XML generation was being handled asynchronously by the job scheduler on all save operations, so it can be served up when requested instead of being generated on the fly. It can be tricky to remove fields programmatically while still maintaining valid EAD, as we also have to consider parent elements, etc - but it can be done! I'm away at a conference this week with spotty access, but feel free to contact me off-list if your institution wants to follow up on the possibility of sponsoring this development.
Regards,
--
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-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@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/CAF8JE%3DqCOSDqaVh4CZadVwoMgx2W3oTtK1U%3DdFhWW71%3D-TbxJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.