I have a group that has a boundary feature that they update on an annual basis. These boundaries are used to determine permits and applications for that year. I am wondering how to make an authoritative dataset for this type of data, that changes on an annual basis, but previous versions of the data are still relevant. I would like to maintain the most current boundary on Enterprise, and have that published and available publicly, but am not sure I want to be maintaining multiple very similar boundaries.
How do other organizations handle and organize data of this nature? Currently we have file geodatabases in "archival" folders that are read only to hold the previous iterations of the data, with the newest boundary being saved on Enterprise.
