isawnyu / pleiades-gazetteer

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.
https://pleiades.stoa.org
11 stars 0 forks source link

pleiades-gazetteer

This repository provides a home for tickets and other planning documents for the Pleiades gazetteer of ancient places, a joint project of the Institute for the Study of the Ancient World at New York University, the Ancient World Mapping Center at the University of North Carolina at Chapel Hill, and volunteer scholars, students, and enthusiasts around the world.

Reporting bugs and requesting enhancements

Please feel free to open an issue in our issue tracker describing your difficulties and/or suggesting new features. Please note that there is a help and documentation section on the Pleiades site. You may also be able to get assistance (depending on availability of team members -- we don't have support staff) on the Pleiades IRC Channel.

Pleiades 3

At the beginning of August 2015, the National Endowment for the Humanities announced the award of a $322,615 grant for major upgrades and improvements to the P​leiades gazetteer of ancient places. More information about the award is available on the ISAW News Blog. A copy of the proposal narrative has been posted online in PDF format. Tickets (issues) related to the grant-funded work are kept in the main issue tracker on this repository; they are labeled "p3". Other documents related to the Pleiades 3 effort may be found in the pleiades3 branch of this repository.

Code: Plone Buildout

Pleiades runs on Plone. With plenty of add-ons and customizations. Relevant repositories are listed in the following sections.

The Plone buildout for Pleiades is Pleiades 3 Buildout. The pleiades-production.cfg config file is used on production; it extends buildout.cfg and production-versions.cfg. Note that the buildout makes use of a static package distributions directory at http://atlantides.org/eggcarton/.

Other Pleiades Code for Plone

The following packages are developed by the Pleiades project and are included in the production buildout. Links to repositories are provided and version numbers, where pinned in the buildout, are indicated.

Pleiades Atom (pleiades.atom)

Pleiades Bulkup (pleiades.bulkup)

Pleiades CAP Grids (pleiades.capgrids)

Pleiades Content Ratings (pleiades.contentratings)

Pleiades Dump (pleiades.dump)

Pleiades Entity

Pleiades Geographer

Pleiades Iterate

Pleiades JSON

Pleiades KML

Pleiades Neighbors

Pleiades Normalizer

Pleiades Notre Dame

Pleiades Open Layers

Pleiades Place Match

Pleiades Policy

Pleiades Portlet for Flickr

Pleiades Portlet for Pelagios

Pleiades RDF

Pleiades Reconciliation

Pleiades Sitemap

Pleiades Theme (pleiades.theme)

Pleiades Transliteration

Pleiades Vaytrou Index

Pleiades Vocabularies

Pleiades Workspace

Third-Party Code Used in the Plone Buildout

[CTypes]

Keytree

[PyProj]

[Python LDAP]

Shapely

[Simple JSON]

[Tornado]

[ZGeo Atom]

[ZGeo Geographer]

[ZGeo KML]

[ZGeo Plone Atom]

[ZGeo Plone Geographer]

[ZGeo Plone KML]

Other Pleiades-Specific Website Components (i.e., non-Plone)

BA Bibl Web

CAP Grids Web

Pleiades API

Pleiades Frontpage

Pleiades GANE

Pleiades Portlet References

Other Pleiades Code

Pleiades Update Overlays

Possibly moribund/obsolete code

Pleiades Keytree

About

Pleiades provides open access to the most comprehensive geospatial dataset for antiquity available today. It serves as an indispensable component of at least 40 other important digital humanities projects, ranging from online editions of primary sources for students to expert systems supporting advanced research in fields like archaeology, epigraphy, and numismatics. It also constitutes a core resource for classroom activities focused on ancient geography.

Find out more on the Pleiades website: http://pleiades.stoa.org.

Pleiades has received significant support from the National Endowment for the Humanities since 2006. Any views, findings, conclusions, or recommendations expressed in this publication do not necessarily reflect those of the National Endowment for the Humanities.