Mayan EDMS 1.0 TO DO list

[Roberto Rosario]

Google document detailing the list of task targeted for the next release.  View and comment directly on the document or on this thread.

https://docs.google.com/document/d/19F5fUjAvsAHXLcPWOGnIpYtWAHQ_CwWLNi6jv8oeQCc/edit

[silopolis]

Hi,

First things first, let me congratulate you for creating what seems o be a _very_ nice piece of software and filling a hole in the ECM land: a common/standard technologies based, feature rich, _python_ written EDMS !

Now I have again one more thing on my todo: install and broadly test Mayan !

On Tuesday, January 15, 2013 7:10:15 AM UTC+1, Roberto Rosario wrote:

Google document detailing the list of task targeted for the next release.  View and comment directly on the document or on this thread.

https://docs.google.com/document/d/19F5fUjAvsAHXLcPWOGnIpYtWAHQ_CwWLNi6jv8oeQCc/edit

Considering the very effective list of features already available, my only questions at this stage are from the integration point of view:
   * I don't see any mention of any API on the feature page, nor in the doc. If I have skimmed over it, could you please point me to the relevant reference ?
   * With the release this week of LibreOffice 4.0 (https://wiki.documentfoundation.org/ReleaseNotes/4.0#Core) supporting CMIS (https://en.wikipedia.org/wiki/Content_Management_Interoperability_Services), this would be the one feature I'd ask for, even before document workflows (which I can handle outside Mayan as soon as I have an API). This would provide a standard, powerfull, domain specific API, AND, would immediately leverage user experience with a "transparent" desktop integration.

Once again congratulations for the huge work already done and furthermore, thank you very much for open sourcing. Keep it on !

Bests
Jérémie

[Roberto Rosario]

Hi Jérémie,

Thanks a lot for that, hope Mayan proves useful for you!

Yes the API is not documented because it really wasn't much of an API.  Now upgrading to the lastes Django Restful library more models have been exposed (https://github.com/rosarior/mayan/blob/development/mayan/apps/api/serializers.py) and there is also a permission for granting access to the API to specific users: https://github.com/rosarior/mayan/blob/development/mayan/apps/api/permissions.py#L27.  I will document the endpoints ( 4 at the moment) of the new API in the following release.

CMIS and WebDAV are two big ¿? to me, I've been trying to find some Python server libraries to no avail.  I would really like to add support for these two standards, but they seem just out of reach to me at the moment due to a lack of knowledge/experience/sample code.

Awesome thanks a lot!

--Roberto

[silopolis]

Hi Roberto,

Le jeudi 28 février 2013 07:50:34 UTC+1, Roberto Rosario a écrit :

Yes the API is not documented because it really wasn't much of an API.  Now upgrading to the lasts Django Restful library more models have been exposed (https://github.com/rosarior/mayan/blob/development/mayan/apps/api/serializers.py) and there is also a permission for granting access to the API to specific users: https://github.com/rosarior/mayan/blob/development/mayan/apps/api/permissions.py#L27.  I will document the endpoints ( 4 at the moment) of the new API in the following release.

Here are good news ! :-)

CMIS and WebDAV are two big ¿? to me, I've been trying to find some Python server libraries to no avail.

Had these in my bookmarks:
https://code.google.com/p/pywebdav/
https://code.google.com/p/wsgidav/

For CMIS, sadly, even after an intensive tech watch I made at the time I posted my last message, I couldn't find any server implementation in Python :( May be OpenCMIS reference implementation could be glued someway?
 

I would really like to add support for these two standards, but they seem just out of reach to me at the moment due to a lack of knowledge/experience/sample code.

Whish I could help but I sadly am skill/time constrained too.

Keep it on
Bests

[Jason Priebe]

Roberto:

This is a great product, and you have a very ambitious list of 1.0 features mapped out.  I would like to throw in a vote for a couple of features that would be very useful to us:

 - multiple instances of metadata (you already have this in your list - nice)

 - "semi-constrained" lookups - allow the user to enter free text, but provide auto-completion suggestions to help users maintain consistency

 - a date/time metadata type (with some sort of formatting capabilities - you don't always need the date *and* the time)

I already filed a couple feature requests in your github issue tracker.  Sorry for bombarding you with suggestions.

I am willing to tackle some of this work if you are interested.

Keep up the great work!

[Roger Nutbeam]

Semi-constrained lookups would be VERY useful for preventing redundant data being entered. For example, a lookup in a client name field would help prevent such things as the same client being entered with a comma before an LLC, as well as the client name being entered without the comma before the LLC.