I am starting a project archiving many (1,000+) photographs, negatives, and documents as part of a family history project. I want to add context to all these documents, so I am looking for a simple document management system (that will hopefully be around for a loooooong time). I am looking for a DMS that is ready for a small production environment - maybe 10-20 users and contributors.
The highlights of how I see this system working: (1) upload of a single document and bulk upload of many documents (pdf or tiff) - interface should be web and CL (is ssh to server needed); (2) ability to associate a textual (or audio??) annotation to each document; (3) easy search (ie Google style single text box entry with search terms) of the annotations and any tags associated with the documents; (4) thumbnail display of the search results in a browser; (5) display of a selected document and annotation in a browser; (6) account roles/groups so some can edit and others just view; (7) download documents from browser and print annotations; (8) browser based annotation editing with simple editing tools (indent, font styles and sizes, headings, etc.); (9) support LibreOffice and MS Windows uploads of annotations if the user prefers that method as opposed to browser editing. I am familiar with django and have written and deployed a few apps using Debian, mysql, south, fabrik, virtualenv, apache and wsqi. However, I do not want to make this project a development project. I really want it to work out of the box with no tweaking. All of the other users only know python as a snake, so they are not capable of making any tweaks or changes. I do not want to go through a lot of app/model updates that break Mayan and need a lot of developer intervention. This is not a project that pays me anything, so my day job comes first! There are lots of java and php solutions out there, but since the budget for the project is USD 0.00, I feel that a django/python deployment will be cheaper to host is the long run than a java based solution. However, I have also written and deployed JSP/servlet apps in the past. I do not want to learn php....;) My questions are: 1. Is Mayan ready for production for the application I have described above without a developer in the wings ready to fix things that break at every software update? I prefer to make software updates as they come out to keep the app secure...and I don see that your updates separate any security updates from feature updates. Not a criticism, the project is new and improving quickly. 2. I am more familiar with MySQL than Postgres, but I see in some of the documentation that you recommend Postgres over MySQL (lack of transaction support in MySQL). Given my small user base and low traffic volume, will MySQL be an issue? 3. How does one backup a Mayan installation? 4. Have you thought about migration strategies to another DMS? In other words, if I need to move to another DMS, is it possible without a lot of pain to export the documents and associated annotations, tags, etc. (text files??) for import to another system? 5. If the answer to 1 is ¨not yet ready for prime time¨, then can you recommend another solution? Thanks! Mark -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
