Mayan (software)
web-based document management system
Mayan (or Mayan EDMS) is a free and open-source document management system. It stores uploaded files as documents, extracts their text using optical character recognition, organises them with user-defined metadata, tags, cabinets and automatically maintained indexes, and moves them through configurable workflows. It is written in Python using the Django web framework and is distributed for deployment with Docker.
Development began in February 2011. The software was released under the Apache License 2.0 from 2014 until January 2024, when the project relicensed to version 2 of the GNU General Public License. It has been used by government agencies, universities and research collaborations, including records systems of the Tennessee Department of State, a software engineering course at Carnegie Mellon University, and the British Library's digital preservation infrastructure.
History
Mayan started as a project whose only requirement was the storage of PDF files for a government agency transitioning to an all electronic registration process and has grown into a general system since then.
In August 2012, while the software was distributed under the GPL, its developer withdrew the development code from public repositories after unauthorised forks were distributed, one of them offered under a commercial licence. The Register reported the withdrawal and the accompanying list of alleged licence infringers.
Version 1.0 was released in August 2014.
This brief starts where responsible research should: with the source description of “Mayan (software)” as web-based document management system. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as web-based document management system. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 7, 2026. The linked authority identifier is Q6796823. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2011, 2014, 2024 and 2012.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Mayan (software)”, its source revision and the description used here.
- Expand the search: follow Mayan (software) primary sources, Mayan (software) archive and Mayan research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Mayan (software)”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Mayan (software)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.