This is similar to #2027, but not as obvious as something needed to do. Right now NEON surface datasets are set using user-mods. We have a line that gives the creation dates for all NEON files and we update all files even when we only need one to be updated. We also have a separate copy of this setting for FATES.
If we refactor to move this to inside of namelist_defaults, we could easily have a line for each site. Which would make it easily possible to change date stamps for individual sites. And the logic for FATES could be embedded at that level as well. Which would remove some of the need to replicate the user-mods for FATES.
The downside of creating all files isn't too bad, since these datasets are small. But, for dataset providence it would be beneficial to only update the datasets that really need to, so then you can understand the history of needed changes more clearly.
This is similar to #2027, but not as obvious as something needed to do. Right now NEON surface datasets are set using user-mods. We have a line that gives the creation dates for all NEON files and we update all files even when we only need one to be updated. We also have a separate copy of this setting for FATES.
If we refactor to move this to inside of namelist_defaults, we could easily have a line for each site. Which would make it easily possible to change date stamps for individual sites. And the logic for FATES could be embedded at that level as well. Which would remove some of the need to replicate the user-mods for FATES.
The downside of creating all files isn't too bad, since these datasets are small. But, for dataset providence it would be beneficial to only update the datasets that really need to, so then you can understand the history of needed changes more clearly.