collectionsonline
collectionsonline copied to clipboard
Revisit how we build location / on display list for facets
I'm not sure the current method of periodically updating the index / building this list via npm run index-update
isn't going to work long term. New locations are regularly added and their names updated and waiting for this command to be run manually will cause confusion / concern if those changes aren't reflected inline with the updated to other collection data.
Can we add npm run index-update
to the deploy process? or use Lamda?