If this is approved, then this must also be updated in the EAD importer/exporter. The screenshot attached would produce the following EAD2002, for example, upon serialization:
: i still have to test the EAD3 export option, but I assume that revision descriptions would be exported something like the following:
Again, if this feature were added to the staff interface, then it would need to follow the same EAD import/export logic whereby anything with audience="internal" is unpublished, and anything without it is considered to be published by default (which is also how things are described in the EAD spec / tag library).
Also adding , as discussed on the call: when the "Revision Description" feature was added as a subrecord in ASpace, it never got a section/link in the side navigation menu in the staff interface (I'm not sure if this was intentional or not, but it seems like it should have a link, since it's the only section that doesn't). Where this feature is located now, the link should occur after the "Finding Aid Data" link, and before the "Related Accessions" link. Of course, SIEWG might recommend an entirely different location in the staff interface It seems to me that it could also fit naturally at the end of the Finding Aid Data section, but there may be technical reasons for why it wasn't added there in the first place.
I should also add that if this approach is taken, that I think it would make sense to consider all of the pre-existing revision descriptions to be unpublished by default, which would accomplish the result wanted by even without having to install a plugin to suppress that data.
DevPri recommends that the revision statement be made more configurable.
I tested by adding a revision statement to an existing resource and then publishing the resource. The revision statement is still part of the "publish all" set and will be made public via that operation, though I could manually untick the publish checkbox and suppress it from the PUI. I'm not sure if this is the intended behavior or if it should default to not published even when "publish all" is selected.
On a related note, it would be nice if the publish all operation could be configured to exclude certain fields - perhaps that array could be defined in the config file.