Mayan 1.1 released

[Roberto Rosario]

I'm pleased to announce the immediate availability of Mayan EDMS 1.1.

Many new features and fixes made it into this release with over 70 issues closed, almost 800 commits and 4 months of work, the additions are many, but here are some of the changes that I think most users are looking forwards to:

• A complete move to Celery for background task processing, including thumbnail generation.
• Much expanded REST API.
• Sending documents link or documents as attachments via email.
• New release cycle with focus of maintenance and support.
• Receiving documents via email (IMAP and POP supported).
• Addition of watched folders.
• No more segfaults when generating PDF.
• Browser memory usage reduction, hundred page documents load and display much better.
• Per user language and timezone settings.
  
• Optional and required metadata per document types.
• Explicit testing against PostgreSQL, MySQL and SQLite.
• Per document language setting.
• Metadata validation and parsing.
• Document workflows.

Big thanks to all contributors, testers, translators, and mailing members, and big thanks to our two corporate sponsors: Cryptico Corp. and S.A. LLC, their support allowed me to work full time on Mayan EDMS these past 4 months.

 - Release Notes: http://mayan.readthedocs.org/en/latest/releases/1.1.html

 - Downloads: https://pypi.python.org/pypi/mayan-edms

 - Code: https://github.com/mayan-edms/mayan-edms

 - Mailing list: https://groups.google.com/forum/#!forum/mayan-edms

 - Support chat: https://gitter.im/mayan-edms/mayan-edms

 - Homepage: http://www.mayan-edms.com/

 - Issues, bugs: https://github.com/mayan-edms/mayan-edms/issues

Enjoy Mayan EDMS 1.1!

[Mathias Behrle]

* Roberto Rosario: " [Mayan EDMS: 994] Mayan 1.1 released" (Tue, 10 Feb 2015
12:21:28 -0800 (PST)):

> Enjoy Mayan EDMS 1.1!

For sure, big thx!

--

Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6

[Cort Comish]

Hi Roberto and others who have contributed to this release,

Thanks for your great work. I have been testing Mayan EDMS 1.0 for a few months and have been very impressed. I just installed v1.1 and so far everything looks good. Two questions regarding the new release:

1) Is it possible to allow multiple list values of a document attribute be assigned to a document (e.g. for metadata "Object" allow values "Building A", "Building B" or both "Building A" and "Building B" be assigned, as some documents might apply to both buildings)? The only workaround I have found so far is to upload the document twice, once for each building. Adding an entry "Buildings A and B" to the attribute list is no good, since the document won't appear under the index for Building A and Building B.

2) Why has the filesystem document indexes mirroring feature been removed? Is it coming back or has / will it be replaced with something else? This was / is one of the most useful features to quickly access the documents without having to go through a web browser.

Best regards

Cort Comish 

[Mathias Behrle]

* Cort Comish: " [Mayan EDMS: 996] Re: Mayan 1.1 released" (Wed, 11 Feb 2015
12:22:56 -0800 (PST)):

Hi Cort,

> 1) Is it possible to allow multiple list values of a document attribute be
> assigned to a document (e.g. for metadata "Object" allow values "Building
> A", "Building B" or both "Building A" and "Building B" be assigned, as some
> documents might apply to both buildings)? The only workaround I have found
> so far is to upload the document twice, once for each building. Adding an
> entry "Buildings A and B" to the attribute list is no good, since the
> document won't appear under the index for Building A and Building B.

Instead of uploading twice I would recommend you to create more indexes like
Object1, Object2, Object3...

Cheers,
Mathias

[Cort Comish]

Hi Mathias,

Thanks for the quick response, I'm not sure though what you mean. Do you
mean defining an independent metadata type for each object, for example
"Building A" with values true or false, "Building B" true or false,
etc.? That would work but is not very usable with lots of metadata types
and values. Or is there some other way to create indexes that helps to
simulate or use multiple values for a metadata type?

Regards
Cort

[Mathias Behrle]

* Cort Comish: " Re: [Mayan EDMS: 997] Re: Mayan 1.1 released" (Fri, 13 Feb
2015 20:11:00 +0100):

Hi Cort,

didn't test that, my idea was to create two metadata types for the same object,
let's say object1 and object2, assign them different buildings and then perhaps
to say in the index something like
document.metadata_value_of.object1 + ', '+ document.metadata_value_of.object2

Cheers,
Mathias