In principle it is best to have completely opaque identifiers for the
web, and a separate system (which can be a simple as a couple of
database tables) to keep track of the mapping. This is useful not as
much for obscuring URLs (security through obscurity may work for
short-term embargo as in your case, but becomes brittle for permanent
URLs) as it is for sustainability. If your public URLs contain e.g. a
TMS and/or NetEx ID, if you migrate out of either system you may not be
able to retain those identifiers and will break all your public URLs.
Stefano
On 5/2/20 6:46 AM, Heidi Quicksilver wrote:
I’m not sure if this will be helpful or not but I know that there is a way
to create URL‘s that are not predictable. We did this on the last website
that I worked on because we had to create content that was super secret
before it was publicly released and we had people who were scraping our
site to try and figure out what the content was before we released it. We
were working with Gavin and Neil at Cogapp for the web development. Perhaps
they can help explain how they helped us create unpredictable URLs for web
pages. We were using Drupal 8.
Heidi Q
Perez Art Museum Miami
Previously Rock & Roll Hall of Fame
hquicksil...@pamm.org
_______________________________________________
You are currently subscribed to mcn-l, the listserv of the Museum Computer
Network (http://www.mcn.edu)
To post to this list, send messages to: mcn-l@mcn.edu
To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l
The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/
