Order of Entry / Studios and Facilities

[japierce1028]

Should we add new facilities / studios to top of list for ease of finding / entering in JSON database? The user sorting ability seems to remove need to have them manually sorted. It would require confirmation of uniqueness of code.

[SteveLLamb]

A couple things. There is already code I believe to confirm the uniqueness of the code values. Also, the ordering is automated after a push is done to make the JSON canonical in order to maintain file integrity. The "manual" sorting in the JSON file as we put values in is just to make the file canonical from the get go, to ensure the user is entering in proper values, and to help us see as we put them in that they are unique code values. It's always better to make sure data is good as it goes in, and let the system validate it.

On the pages, the initial sort is always by code.

Playing devil's advocate - as far as "new" items going to the top for ease - at what point would we decide that a code is no longer "new" and let it being sorted by code and not be at the top? Search in both the web page, and text editor, as well as the google sheet, removes any need for an order that is not canonical IMO.

[japierce1028]

So if we can enter new facilities/studios at the top, I'm good. I don't care where they get entered AFTER they are approved. Looks like I CAN enter at the top, so I'm good with this. We can close the issue if that is right.

[SteveLLamb]

I believe it will not pass checks if you do that fyi.

[japierce1028]

So the issue is still open. I would like the ability to enter at the top of the registry. But that's just me. If there is a reason that we need to scroll down 1,000 entries to enter a "ZZZ" facility, then maybe we could allow entry at the top.

[palemieux]

GitHub can be configured to auto-sort on each commit. Downsides:

• development work
• what the user submits is not actually what is committed

EDITED: clarity