This repository provides a home for tickets and other planning documents for the Pleiades gazetteer of ancient places. Code is kept in multiple other repositories.
Back in the day, when we used Barrington uris in the form http://atlantides.org/batlas/abrotonum-sabratha-35-e2 because Pleiades ids were not yet stable and easily discoverable, the intention was that those would redirect or be resolved to the correct Pleiades ids. The IRT 2009 EpiDoc files contain many of these URIs, for example. At one time, I'm sure the redirects worked.
If you visit http://atlantides.org/batlas/abrotonum-sabratha-35-e2 now, however, it returns a 404, with a link to a no-longer-extant issue in the Atlantides trac instance for information, which suggests that something in the pipeline has broken. This makes the BAtlad ids pretty useless, along with all GeoLinks from IRT, so it would be great if this could be rescued, and redirects put back into place. (Should these be transparently visible in Pleiades pages as well, however obsolete they may be?)
Back in the day, when we used Barrington uris in the form
http://atlantides.org/batlas/abrotonum-sabratha-35-e2
because Pleiades ids were not yet stable and easily discoverable, the intention was that those would redirect or be resolved to the correct Pleiades ids. The IRT 2009 EpiDoc files contain many of these URIs, for example. At one time, I'm sure the redirects worked.If you visit http://atlantides.org/batlas/abrotonum-sabratha-35-e2 now, however, it returns a 404, with a link to a no-longer-extant issue in the Atlantides trac instance for information, which suggests that something in the pipeline has broken. This makes the BAtlad ids pretty useless, along with all GeoLinks from IRT, so it would be great if this could be rescued, and redirects put back into place. (Should these be transparently visible in Pleiades pages as well, however obsolete they may be?)