This application is still under heavy development (by which I mean "it still needs a ton of work before it does anything useful", as opposed to "I'm constantly working on it"). For now, I'll use this readme to describe what I would like it to do, rather than what it currently does. It is also under "heavy development".
Storing archaeological data
ArchCRM should retain the flexibility of an Excel-based "database", while making common data entry tasks easier. The data entry interface will support things like field locking to make it easier to hand-enter large numbers of similar artifacts, importing from various formats such as CSV, and custom functions to pre-fill selected fields (such as an auto-incrementing accession number, as a very basic example).
ArchCRM should support the concept of an assemblage as a custom set of filter criteria. Often this will mean defining an assemblage like "Site A Bifaces" as a set of two filters - all artifacts where site = "Site A" and type = "bifaces". Filter criteria will be flexible enough to create more granular assemblages, however, such as "Large Bifaces from Modoc County" - all artifacts where type = "bifaces", length greater than 15cm, and county = "Modoc".
This is the part I'm not so sure about. Certainly it should be easy to create tables and graphs from the data in the system and derive basic statistics, but there are likely other analyses that could be done that I'm not thinking of. So any parts of the application that deal with analyzing data should be as flexible as possible to make it easy to extend.