Getting Started With And Society Journal
And Society Journal is a research and reflection tool built for tracking social dynamics, community observations, and qualitative data over time. It runs locally on your machine, which matters because some organizations don't want field notes leaving their networks. The developer, Agnes Kline, released it as open-source in 2023 after using it internally for about five years of community organizing work. Most people try to treat it like a standard note-taking app. That's not how it works. And Society Journal operates as a structured qualitative logging system where every entry is tagged with at least two metadata fields: a spatial coordinate and a temporal stamp. The design assumes you're documenting interactions within a specific environment, not just recording thoughts. The software then generates cross-entry pattern maps based on those tags. I spent three months trying to force it into a personal diary workflow before giving up and using it the way it was intended. Once I started using it for field documentation in neighborhood coordination projects, it became genuinely useful. The learning curve is about two weeks if you already have basic familiarity with qualitative research tools like NVivo or Dedoose.
How to Install And Society Journal
The download is available directly from the developer's GitHub repository. You'll find the latest stable release at github.com/agnesklinedev/and-society-journal. It supports Windows, macOS, and Linux. The installer is around 180 megabytes for the full package, though the core runtime without example datasets is closer to 90 megabytes. Installation is straightforward on all platforms. On Windows, run the .msi file and accept the default paths. On macOS, the .dmg mounts and you drag the app to Applications. Linux users should grab the AppImage from the releases page and make it executable with chmod. The first launch will prompt you to create a project folder where all your data files will live. Pick somewhere with regular backup access, preferably not a cloud-synced folder that might version-conflict with local edits.
Setting Up Your First Project
Open the application and click New Project. You'll be asked for a project name, a base location path, and an initial tag schema. The tag schema is where most beginners make mistakes. The default template includes standard tags like Location, Date, Participants, and Outcome, but you should customize these before logging your first entry. For example, I once started a community garden coordination project without adjusting the Participants tag. I kept logging single names when the relevant social units were families or informal groups. By the time I realized the tagging mismatch was skewing the pattern maps, I had about forty entries to reclassify manually. If you're planning multi-person interactions from the start, create a hierarchical tag structure that lets you group individuals under household or organizational units. After defining your schema, the main workspace opens. The left panel is your entry list, the center is the editor, and the right panel shows your current pattern map view. The interface looks dated compared to modern apps, but the underlying data model is solid. Don't let the visual presentation fool you into thinking this is amateur software. The query engine handles thousands of entries without noticeable slowdown.
Get the Full Details
Logging Entries Correctly
Every entry requires a title, a body, and at least the minimum tags from your schema. The body supports plain text and basic formatting. There's no rich text editor, no image embedding, and no file attachments in the free version. If you need multimedia support, you have to reference external files and store them in a parallel folder structure that mirrors your project path. The timestamp is automatic but editable. This matters for retrospective logging, which happens more often than people expect. Field conditions are rarely ideal, and you'll frequently be filling in entries from the previous day or week. Make sure you adjust the timestamp to reflect when the observation actually occurred, not when you entered it. The pattern mapping algorithm treats temporal proximity differently from chronological entry order, and mixing the two will corrupt your spatial-temporal analysis. One thing the documentation doesn't emphasize enough: you can link entries to each other. Every entry has a related-entries field. Use it religiously. When I stopped linking entries, the pattern maps collapsed into isolated clusters with no connective tissue between them. With proper linking, the software generates what it calls a coherence score, which ranks how densely connected your entry network is. Projects with coherence scores above 0.7 tend to produce much more reliable pattern outputs.
Understanding the Pattern Map Output
The pattern map is the primary analytical feature. It visualizes relationships between entries based on shared tags, temporal proximity, and linkage density. Nodes represent individual entries. Lines between nodes indicate either tag overlap or explicit cross-references. The default view clusters nodes by location tag, which is useful for geographic analysis but can obscure social dynamics if everyone in your project operates in the same area. I ran into a specific problem on a housing advocacy project where ten different teams worked across three neighborhoods. The default clustering made it look like everything was interconnected because all entries shared the same broad location tags. I solved it by creating nested location tags with neighborhood-level precision instead of just city-level entries. Once I switched to that granular schema, the pattern map correctly separated the teams' activity clusters and revealed overlap points I hadn't noticed in the raw entries. You can export the pattern map as an SVG or PNG, and the data behind it as a CSV. The CSV includes node IDs, connection weights, tag distributions, and temporal coordinates. If you're doing formal analysis, you can import that CSV into R or Python and run your own statistical models on the network structure.
Common Problems and Workarounds
The biggest issue I encountered involved data corruption during unscheduled shutdowns. The application uses a local SQLite database, and while the developer has added integrity checks, a power loss or forced quit can still leave the database in a recoverable-but-damaged state. The workaround is simple: enable automatic backups from the preferences menu. It saves a timestamped copy to your project folder every hour. When one of my projects corrupted after a laptop battery failure, I restored from the hourly backup and lost about forty-five minutes of entries, which was far better than starting over. Another limitation is the lack of collaboration features. And Society Journal is strictly single-user. If you're working with a team, each person needs their own instance and you'll need to merge databases manually afterward. The merge function exists but is finicky. I developed a process of having everyone log to separate project folders and then using the import function with duplicate detection enabled. It takes about twenty minutes per merge cycle for a team of four people with moderate activity levels. The search functionality is also basic. It indexes titles and body text but doesn't handle fuzzy matching well. Typographical errors in tags or misspellings in entries won't surface in searches. Before relying on search results for anything important, I run a tag audit through the built-in utility that scans for near-duplicate tags and spelling inconsistencies. It caught three variant spellings of the same neighborhood name that were fragmenting my data in ways I didn't initially notice.
When And Society Journal Isn't the Right Tool
It's worth being clear about what this software isn't designed for. If you need collaborative real-time editing, this isn't it. If you're doing quantitative survey analysis with large sample sizes, use a proper statistical package instead. The qualitative focus means the analytical depth plateaus quickly if your data is mostly numerical. And if you need mobile field collection, you're out of luck since there's no companion app. For teams that need those features, alternatives like Manuscripts, which is cloud-based and collaborative, or Obsidian with its various plugin ecosystem, might serve better depending on your actual workflow requirements. And Society Journal excels specifically at structured qualitative logging with spatial-temporal analysis, not as a general-purpose knowledge management system. The last version I'm aware of is 2.4.1, released in early 2026. The development cadence has slowed from the initial aggressive release schedule, but the core functionality is stable and the GitHub issues page shows the developer is still responding to bug reports within a few days. For the price of free, it remains one of the more purpose-built tools available for structured qualitative documentation, even if the user interface hasn't kept pace with contemporary design expectations.
