Finding Data (including legacy versions)

This page assumes you know the legacy Perseus document name for a particular file and are trying to find it's URN and/or location in the CVS repo, or the other way around.

Some resources that are most frequently helpful in finding files and document names include:

• The P4 to P5 Text Migration Spreadsheet
  _While the P4 to P5 Text Migration Spreadsheet is mostly deprecated with respect to tracking files (for more on current ways of tracking files, see Tracking Data), it can still be a good place to look if you're trying to find a particular text. _

• classics.xml

• The Perseus Catalog
  _The atom links for particular editions or works are frequently the most helpful. You can find them under "Alternate Representations" in the upper righthand corner after you've clicked on a particular author, work, or edition. You can also find them directly by URN. Here is an example. There is also an ATOM Response API that can be programmatically searched; see here for more information. _

• The CVS repo
  _You'll need to have a Tufts UTLN to gain access to the CVS repos with legacy data, or ask someone with access to find the file for you. If you choose to do the latter, find out the CVS file name from The P4 to P5 Text Migration Spreadsheet, and enter an issue in the appropriate Git Repo.

• The Perseus canonical repos
  _The Perseus canonical repos are kept in the PerseusDL Github account, organized by language of the original edition. For example, canonical repos available right now include:

  • canonical-latinLit for Latin literature
  • canonical-greekLit for Ancient Greek literature
  • canonical-itaLit for Italian literature
  • canonical-norseLit for Norse literature (which, by the way, is fully EpiDoc/CTS compliant, fairly large, and would make an excellent best-case repo for testing services)
  • canonical-angLit for Old English literature
  • canonical-farsiLit for Farsi literature_