Explore using logical IDs (timestamps and slugs) in URLs #273
Description
Currently to access a specific frame in a specific event, you need to know the actual object IDs in the current database.
During development the actual object IDs can change when recreating environments. It would be very helpful if URLs looked something like this:
http://localhost:3000/projects/vermont-1/sessions/2022-05-01?capture=20220501T05:00:01&occurrence=Actias%20luna%202
Instead of:
http://localhost:3000/projects/1/sessions/34?capture=46906&occurrence=232
At a very minimum, the timestamp of a capture would be very helpful for troubleshooting. Readable project slugs would also be nice for users.