periodCollection -> authority (naming) about periodo-data HOT 5 CLOSED

I assume this won't be retroactively applied to past versions of the dataset (& patches). That means that we will need to write code that deals with both periodCollection/periodCollections and authority/authorities

from periodo-data.

Is that an argument against doing it, or are you just making an observation?

Also isn't the same true of all the data model changes that aren't strictly additive?

from periodo-data.

I suppose it would be possible to maintain a set of functions for transforming old invalid data into valid data for display; the changes are all documented at https://github.com/periodo/periodo-validation/tree/master/fix

from periodo-data.

It was an observation. To this point, as far as I can recall, we've only made changes that are additive (in terms of the data model). Checking for periodCollection vs authority would be a good marker for needing to do that sort of conversion.

It's not a big deal with operating on the dataset as a whole-- it'll just get tricky for visualizing diffs whose endpoints cross that threshold. (Not just for this change, but for all of them that we're doing).

from periodo-data.

Done in staging by https://github.com/periodo/periodo-validation/blob/master/fix/renaming.js

from periodo-data.