-
Notifications
You must be signed in to change notification settings - Fork 1
Options Evaluated Before Creating Doc Meta
Working with data stored on Google Drive requires that one work via Google's API. These APIs change from time to time (in 2013, for instance, Google initiated changes to their API for Google spreadsheets that changed the way several basic file manipulation operations could be performed, necessitating code re-writes to dependent software).
Mayan EDMS is a great tool with an active community. It offers a lot of handy ways for categorizing and tagging data as well as for managing access control, etc. [The access to permission is via the usual Role/Group/User style of thing. You create a Role with permissions, then give that role to a User (or a Group of Users). ]
Mayan EDMS is a great tool with an active community. It offers a lot of handy ways for categorizing and tagging data as well as for managing access control, etc. [The access to permission is via the usual Role/Group/User style of thing. You create a Role with permissions, then give that role to a User (or a Group of Users). ]
Mayan is its own stand-alone (Django-based) software application. As such, it wouldn't work as a 'module' to CCCS' Django application, so any replication of parts of our system dealing with document management would have to separately deploy and configure Mayan EDMS in order to work. Writing code to communicate between our website's presentation of data on the front end and management of data from the Mayan EDMS system requires a bit of extra effort, and the actual management of document data would requires users of the CCCS website to 'log in' to a separate and distinct Mayan EDMS server (while CCCS wishes to manage data from within 'admin').