Falkland CMS is a Curation Management System used to collect, curate, organize and present the knowledge that exists in the world about a particular topic.
Anything that can be unambiguously referenced with a unique identifier such as an ISBN/ISSN, DOI (Digital Object Identifier), PURL (Persistent URL) or URL (Uniform Resource Locator) can be curated with Falkland CMS. The curation process consists of adding metadata information about an item that makes it easier to collect, organize, search, present and exhibit.
Items can be physical things: books, magazines, newspapers, documents, papers, consumer products, artifacts, animals, buildings, people, etc. Or items can be digital or abstract: web pages, articles, chapters, images, audio files, video files, web sites, databases, directories, words, concepts, topics, etc.
Falkland CMS can be used to describe relationships among items and can assist in the archiving and preservation of digital items.
Falkland CMS is for anyone who wants to collect, curate, organize and present the knowledge that exists in the world about a particular topic:
Like one of its inspirations, Omeka, Falkland CMS sits at the intersection between a traditional Web CMS, a Digital Collection Management system, and a Museum Exhibit Management system. Unlike Omeka, Falkland CMS is written in Clojure, ClojureScript and CouchDB, and so it has a certain elegance and panache.
A lot of the software in this domain is produced by people with rich domain expertise, but nontraditional software engineering backgrounds. This often leads to poorly constructed PHP or Perl code that is difficult to use and maintain.
Falkland CMS is a deliberate experiment in going the other direction and having experienced software professionals learn the library science needed to create better software.
These are perfect fits for Falkland CMS:
Falkland CMS is not for everyone, if these describe you, you should probably look elsewhere:
A traditional CMS or WCMS (web content management system) is a system for publishing website content. Key features of a WCMS are:
Falkland CMS has these foundational capabilities, but is not focused on the creation of new content. Instead, Falkland CMS is used for collecting, organizing, curating and presenting existing content.
Falkland CMS supports authoring content, but this content is metadata about existing resources, intended to provide context for the collection, organization, curation, presentation and exhibition of collected resources. You wouldn't run a daily on-line news site with Falkland CMS, like you would with a content management system, but you would use Falkland CMS to collect, curate and present historical or current news reports about a particular topic.
Because of this difference of focus, the acronym that is used for Falkland CMS is Curation Management System.
Standards are very important... and very plentiful. Falkland CMS is flexible so you can use the metadata and interoperability standards most relevant to you. At the same time, Falkland CMS takes an informed, pragmatic and opinionated approach, using widely supported general standards as defaults. If you aren't a card carrying metadata geek, you won't need to make confusing choices from the dizzying amount of potentially relevant standards just to utilize Falkland CMS.
Falkland CMS was created to support Falklandsophile, a complete guide to resources about the Falkland Islands. This is where the name for Falkland CMS came from.
If you're using Falkland CMS, please drop me a note and I'll link to you here.
Falkland CMS is pre-alpha and not yet usable. A usable version is expected sometime in 2015.
You can see the roadmap and check on the development progress on Trello.
Falkland CMS is pre-alpha and not yet usable. A usable version is expected in 2015 and instructions for getting help will be available then.
You can open an issue or feature request in the GitHub issue tracker.
Falkland CMS is distributed under the Mozilla Public License v2.0.
Copyright © 2013-2015 Snooty Monkey, LLC