[Mayan EDMS: 2414] Re: Upgrading from 2.7.3 to NG Versions

[David Kornahrens]

Thanks Michael.  

Since I'm not currently running any of your versions, I'll wait to submit a 
bug request, but right before Roberto went offline, I reported that our 
Xerox machines were rotating some of our uploads (we use SMTP folder watch 
for submittals).  We still are having to manually log in, rotate the 
document and then place in the correct cabinet.

I understand there are some work flow features, but I don't enough about 
either the language or the program to make this run efficiently.  I'm 
excited, beyond excited, that a group of people are picking up and helping 
Roberto.  

Thanks,
David

On Sunday, April 1, 2018 at 4:56:12 PM UTC-4, Michael Price wrote:
>
> Mayan EDMS NG performs initial installation procedures on new databases 
> and performs upgrades if it detects existing data. However, now that 
> Roberto is back and has started merging our work I would suggest you wait 
> for an official release. Both, the official and our Docker image have 
> django-storages included out-of-the-box.
>
> On Sunday, April 1, 2018 at 4:13:06 PM UTC-4, David Kornahrens wrote:
>>
>> Hello community,
>> We are currently on 2.7.3, deployed through Docker.  I am interested in 
>> updating to the latest NG version, if it's supported to upgrade through 
>> Docker.
>>
>> The only concern, we deployed Django Storages and offload media to Amazon 
>> S3.  We need to ensure this stays offloaded to S3 and that our documents 
>> can still be viewed when updated.  We currently have ~5K files.
>>
>> Is this able to be upgraded via Docker?  Or do we need to wait for 
>> official support from the Mayan repository?
>>
>> Thanks,
>> David
>>
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Mayan EDMS: 2412] Announcing Mayan EDMS NG version 2.8

[ericriggs42]

Sure thing. Still the named volume issue is like a thorn. I just want to 
fix it but I still don't get a few things about the way Mayan is packaged 
for Docker. 

On Tuesday, March 6, 2018 at 6:48:51 AM UTC-4, RW Shore wrote:
>
> Actually, the whole volume stuff should be taken as a low-priority 
> suggestion. I've got my service build working now, and was even able to add 
> a new analyzer function (from GIT repo  
> https://gitlab.com/startmat/document_analyzer.git) to an extension of the 
> docker image. I'd rather see a focus on cleanup and new features, rather 
> than on my obscure docker needs.
>
> On Tue, Mar 6, 2018 at 5:22 AM,  wrote:
>
>> Thanks, I'm trying out Debian as the base image and liking it so far.
>>
>> On Friday, March 2, 2018 at 9:47:41 AM UTC-4, Mathias Behrle wrote:
>>>
>>> * ericr...@gmail.com: " Re: [Mayan EDMS: 2288] Announcing Mayan EDMS NG 
>>>   version 2.8" (Wed, 28 Feb 2018 17:49:27 -0800 (PST)): 
>>>
>>> > I managed to get Mayan running using Alpine Linux but the final image 
>>> size 
>>> > was almost the same using Ubuntu. There were too many path and 
>>> > configuration file changes and while Alpine runs well it is not LSB 
>>> > compliant. I don't think it is a fit for something like as complex as 
>>> Mayan 
>>> > and needs to run reliably in business settings. Alpine was a bit 
>>> faster but 
>>> > is missing too many things like language files and fonts (our multi 
>>> > language Office test document doesn't render using Alpine). There are 
>>> > problems with Ubuntu too. Ubuntu 16.04, the recommended version for 
>>> Mayan, 
>>> > is rather old and missing a recent kernel. Moving to a newer version 
>>> breaks 
>>> > too many things. Ubuntu is not careful when it comes to backwards 
>>> > compatibility. RedHat, Fedora and CentOS were a disaster. Many basic 
>>> > libraries are missing and the official recommendation is to use third 
>>> party 
>>> > repositories. No thanks. I'm going to try Debian next, which is very 
>>> secure 
>>> > but also very stable in terms of release continuity (as opposed to 
>>> Ubuntu). 
>>>
>>> JFTR if size matters there are also the *-slim flavors of Debian images 
>>> removing some files usually not needed inside containers. 
>>>
>>> https://hub.docker.com/_/debian/ 
>>>
>>>
>>>
>>> -- 
>>>
>>> Mathias Behrle 
>>> PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6 
>>> AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6 
>>>
>> -- 
>>
>> --- 
>> 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 mayan-edms+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Mayan EDMS: 2412] Re: Announcing Mayan EDMS NG version 2.8

[ericriggs42]

>From what I've seen it is usually a problem connecting to the database. Be 
it hosted or in another docker image. Make sure you specify the database 
driver, the host, user, database name and password correctly. Most of these 
have to be specified for the database container AND the Mayan container.

On Sunday, April 1, 2018 at 4:43:56 PM UTC-4, Michael Price wrote:
>
> Do a 
>
> docker logs 
>
> it should say why it is restarting.
>
> On Sun, Apr 1, 2018 at 7:59 AM, Jos vd Snepscheut  > wrote:
>
>> Hello,
>>
>> I 'm trying to run Mayam EDMS NG 3.0.2 (and 3.0.1) both by using the 
>> docker image and by buildinging it according your instructions.
>> But unfortunatly all my containers keeps restarting.
>> What am I doing wrong?
>> Where can i find help?
>>
>> Thanks,
>>
>> Jos.
>>
>> Op dinsdag 27 februari 2018 11:40:20 UTC+1 schreef Michael Price:
>>
>>> Hi all,
>>>
>>> We love Mayan EDMS and have come to depend on it for our daily work. 
>>> Like many of you we are worried about the effects hurricane Maria has had 
>>> on the development of the project. So we decided to do something about it.
>>>
>>> We gained good knowledge about the internals of Mayan EDMS from customizing 
>>> it for our own use. Looking at the code for the next version we could see 
>>> that much work had already been done. We were confident we could finish the 
>>> remainder tasks to be able to take the code to a point where a version 2.8 
>>> would be possible.
>>>
>>> We contacted Roberto with our idea. While his communication options are 
>>> limited, he nonetheless provided us with some great guidelines. We 
>>> don't pretend our fork to replace Mayan EDMS so we are naming it Mayan EDMS 
>>> NG (Next generation). To make things easier we continued the version 
>>> numbering. 
>>>
>>> So, we are proud to release our work as Mayan EDMS NG version 2.8.
>>>
>>> Our forks is just a continuation of the work already started by Roberto 
>>> for version 2.8. Therefore it is 100% compatible with any existing data. 
>>>
>>> Our work focused on the following areas:
>>>
>>> * Finishing the API test refactor. The purpose of this refactor is to 
>>> test each API function for permission and access failure and success. The 
>>> API tests we also updated to conform with the new API Test class interface 
>>> which reduces a lot of boilerplate code. There are now a minimal of two 
>>> tests for each API function.
>>>
>>> * Some minor permission changes were made when obviously needed such as 
>>> the Workflow Create permission not having any effect.
>>>
>>> * Roberto had already backported the notifications feature to the "next" 
>>> branch and our work just focused on giving the final polish to this feature 
>>> by removing duplication.
>>>
>>> * Some user interface fixes and updated we added. These were inspired by 
>>> discussion on the mailing list and from looking at the Open Paperless fork 
>>> by Tina Zhou.
>>>
>>> * Introduction of the MERC (Mayan EDMS Request for Comment) as a means 
>>> of documenting the internals of the project, proposing features, changes to 
>>> the code as well as to the related process of the project. This type of 
>>> documentation mechanism has been very successful for other things like the 
>>> Internet (RFCs), Python (PEPs) and Django (DEPs) and we are sure it will 
>>> also help Mayan EDMS a lot.
>>>
>>> The repository for this fork is 
>>> https://gitlab.com/Michael.Price/mayan-edms. From there you can examine 
>>> the changes that we made to get the code to release level. Our work is 
>>> available from PyPI as mayan-edms-ng.
>>>
>>> We hope you enjoy it, thank you.
>>>
>>> Michael Price, internals and process
>>> Eric Riggs, user interface
>>>
>> -- 
>>
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Mayan EDMS" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/mayan-edms/Fx8rz4kxPCw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> mayan-edms+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Mayan EDMS: 2411] Re: Situation update

[Michael Price]

Agreed. I too, feel privileged for be able to work on this project and to
be able to learn from an industry leader.

On Sun, Apr 1, 2018 at 5:03 PM,  wrote:

> This is great news!
>
> From what I've been seeing on the net, things are still very bad there.
>
> I speak for myself but I'm sure others feel the same way, you are an
> inspiration. Not only for your work on Mayan, but for all you've
> accomplished, before and after the hurricane. All the sh*t and harassment
> you've had to deal with and still managed to come out on top. I admire you
> very much. Thank you for all your work, thank you for all the lessons.
>
> On Saturday, March 31, 2018 at 2:41:49 AM UTC-4, Roberto Rosario wrote:
>>
>> Big thank you to everybody that has reached out, sent first necessity
>> items, and donated. You have made a situation without precedent much more
>> bearable.
>>
>> This is the situation at the moment (without going into politics or
>> corruption, that has gone to a whole new level of insanity).
>>
>> Utilities are mostly working. There are still a several outages per week
>> but in comparison with having no power, it is a much better situation. Now
>> we can purchase groceries knowing the chances of it spoiling are much
>> lower.
>>
>> Internet and cell phone service are still spotty. We get 1Mbit of
>> download speed. Using heavy ad filtering and compression browsing
>> experience is tolerable but trying to watch streaming content is painful.
>> The same goes for VOIP and video calls. Remote work takes patience.
>>
>> Driving around is still an adventure. A lot of traffic lights are still
>> out. Intersections are like a gauntlet. Patience in the streets is low and
>> people are very prone to road rage. Traffic jams last hours. In those
>> situations phone navigation is useless as there are still many connectivity
>> dark zones.
>>
>> Like most people in the island, my income sources have been gravely
>> affected. Spending now the same amount of time I used to spend on Mayan and
>> my other free projects is a luxury I can't afford. I hope to be able to
>> take some time soon to revise all the work done by the Mayan EDMS NG team
>> and start merging. Since their fork has moved quite a bit ahead of Mayan
>> EDMS, this revision and merge process will be mostly manual. To make the
>> most of the time, I'll focus on bug fixes and outdated version updates
>> (Django, packages, etc), before going into features. From what I've seen so
>> far, they have done a very good job. Their job quality will make mine
>> easier.
>>
>> This has been the worst natural disaster in generations and one of the
>> worse experiences I've had to go through. But we survived it and that's all
>> that matters. We rebuilt our island. And we will rebuild this, our project.
>>
>> Thank again to everybody.
>>
> --
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Mayan EDMS" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/mayan-edms/XKlmMgAniAQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mayan-edms+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2411] Re: Situation update

[ericriggs42]

This is great news!

>From what I've been seeing on the net, things are still very bad there.

I speak for myself but I'm sure others feel the same way, you are an 
inspiration. Not only for your work on Mayan, but for all you've 
accomplished, before and after the hurricane. All the sh*t and harassment 
you've had to deal with and still managed to come out on top. I admire you 
very much. Thank you for all your work, thank you for all the lessons. 

On Saturday, March 31, 2018 at 2:41:49 AM UTC-4, Roberto Rosario wrote:
>
> Big thank you to everybody that has reached out, sent first necessity 
> items, and donated. You have made a situation without precedent much more 
> bearable. 
>
> This is the situation at the moment (without going into politics or 
> corruption, that has gone to a whole new level of insanity).
>
> Utilities are mostly working. There are still a several outages per week 
> but in comparison with having no power, it is a much better situation. Now 
> we can purchase groceries knowing the chances of it spoiling are much 
> lower. 
>
> Internet and cell phone service are still spotty. We get 1Mbit of download 
> speed. Using heavy ad filtering and compression browsing experience is 
> tolerable but trying to watch streaming content is painful. The same goes 
> for VOIP and video calls. Remote work takes patience.
>
> Driving around is still an adventure. A lot of traffic lights are still 
> out. Intersections are like a gauntlet. Patience in the streets is low and 
> people are very prone to road rage. Traffic jams last hours. In those 
> situations phone navigation is useless as there are still many connectivity 
> dark zones.
>
> Like most people in the island, my income sources have been gravely 
> affected. Spending now the same amount of time I used to spend on Mayan and 
> my other free projects is a luxury I can't afford. I hope to be able to 
> take some time soon to revise all the work done by the Mayan EDMS NG team 
> and start merging. Since their fork has moved quite a bit ahead of Mayan 
> EDMS, this revision and merge process will be mostly manual. To make the 
> most of the time, I'll focus on bug fixes and outdated version updates 
> (Django, packages, etc), before going into features. From what I've seen so 
> far, they have done a very good job. Their job quality will make mine 
> easier.
>
> This has been the worst natural disaster in generations and one of the 
> worse experiences I've had to go through. But we survived it and that's all 
> that matters. We rebuilt our island. And we will rebuild this, our project.
>
> Thank again to everybody.
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2410] Re: Upgrading from 2.7.3 to NG Versions

[Michael Price]

Mayan EDMS NG performs initial installation procedures on new databases and 
performs upgrades if it detects existing data. However, now that Roberto is 
back and has started merging our work I would suggest you wait for an 
official release. Both, the official and our Docker image have 
django-storages included out-of-the-box.

On Sunday, April 1, 2018 at 4:13:06 PM UTC-4, David Kornahrens wrote:
>
> Hello community,
> We are currently on 2.7.3, deployed through Docker.  I am interested in 
> updating to the latest NG version, if it's supported to upgrade through 
> Docker.
>
> The only concern, we deployed Django Storages and offload media to Amazon 
> S3.  We need to ensure this stays offloaded to S3 and that our documents 
> can still be viewed when updated.  We currently have ~5K files.
>
> Is this able to be upgraded via Docker?  Or do we need to wait for 
> official support from the Mayan repository?
>
> Thanks,
> David
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2409] Re: Situation update

[Michael Price]

Glad to have you back sir! Excited to see that a lot of our work is being 
merged into Mayan EDMS!

On Saturday, March 31, 2018 at 2:41:49 AM UTC-4, Roberto Rosario wrote:
>
> Big thank you to everybody that has reached out, sent first necessity 
> items, and donated. You have made a situation without precedent much more 
> bearable. 
>
> This is the situation at the moment (without going into politics or 
> corruption, that has gone to a whole new level of insanity).
>
> Utilities are mostly working. There are still a several outages per week 
> but in comparison with having no power, it is a much better situation. Now 
> we can purchase groceries knowing the chances of it spoiling are much 
> lower. 
>
> Internet and cell phone service are still spotty. We get 1Mbit of download 
> speed. Using heavy ad filtering and compression browsing experience is 
> tolerable but trying to watch streaming content is painful. The same goes 
> for VOIP and video calls. Remote work takes patience.
>
> Driving around is still an adventure. A lot of traffic lights are still 
> out. Intersections are like a gauntlet. Patience in the streets is low and 
> people are very prone to road rage. Traffic jams last hours. In those 
> situations phone navigation is useless as there are still many connectivity 
> dark zones.
>
> Like most people in the island, my income sources have been gravely 
> affected. Spending now the same amount of time I used to spend on Mayan and 
> my other free projects is a luxury I can't afford. I hope to be able to 
> take some time soon to revise all the work done by the Mayan EDMS NG team 
> and start merging. Since their fork has moved quite a bit ahead of Mayan 
> EDMS, this revision and merge process will be mostly manual. To make the 
> most of the time, I'll focus on bug fixes and outdated version updates 
> (Django, packages, etc), before going into features. From what I've seen so 
> far, they have done a very good job. Their job quality will make mine 
> easier.
>
> This has been the worst natural disaster in generations and one of the 
> worse experiences I've had to go through. But we survived it and that's all 
> that matters. We rebuilt our island. And we will rebuild this, our project.
>
> Thank again to everybody.
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Mayan EDMS: 2407] Re: Document date and title

[Michael Price]

Hello,

1) They must be using a regular expression feature to extract the data. I
must warn that it is never a good idea to rely on OCR output for data. OCR
is one of those features that will never work 100%. If you do have some
fallback logic to avoid adding garbage data. We could add a post OCR
processing step to add a feature like this. The best place for that would
be the workflow engine. I think there are post OCR triggers. We would need
a regular expression workflow action.

2) A pity. Looks very interesting. I have a lot on my plate but will take a
look to see how difficult it would be add this as a standard app.

3) We added Filters to Paperattor which work a bit like SmartLinks. We are
looking into reusing this method to add workflow trigger filters. This
means that you can make a workflow to trigger the transition and add tags
or extract OCR data for metadata only is certain condition programmed in
the workflow filter is met.

Keep the ideas and use cases coming, they give us a good roadmap to
develops the next set of features.

On Sun, Apr 1, 2018 at 1:55 PM, Raul  wrote:

> Hi Michael,
>
> thanks for your response.
> I finally got my server in place and am ready to rock now.
>
> Regarding my questions:
>
> 1) I was more thinking about something like it is done in paperless (
> https://github.com/danielquinn/paperless).
> Here the date is being extracted out of the OCR content and used as
> document date. Which is a very nice feature.
>
> 2) You are right the addon is outdated.
>
> 3) That would be definitely nice. I the way it is right now the OCR
> content is only used for searching. However, there could be so much more
> you could do with it. Like search for keywords and trigger the auto assign
> to a cabinet or get the document date etc
>
> Am Freitag, 23. März 2018 06:25:11 UTC+1 schrieb Michael Price:
>>
>> Hi,
>>
>> How are you liking version 3.0?
>>
>> Here are the answer to your questions.
>> 1. The file creation data is lost during the upload. These operating
>> system fields and do not persist during upload via web. It could be
>> possible to retain these values if the document is uploaded via a watch
>> folder or staging folder. Since these methods open the file to be loaded
>> into Mayan directly from the operating system the file creation could be
>> read.
>>
>> 2. It is not possible using the normal installation. However I found this
>> online: https://gitlab.com/mayan-edms/document_renaming it seems to do
>> what you want. Haven't tried it and looks outdated. If there is enough
>> interest we could add something like this in our fork of Mayan.
>>
>> 3. Not yet possible at the level you want right now but it is getting
>> there. There is a workflow feature called triggers and another called
>> actions. These allow you to create a workflow that will respond (trigger)
>> based on an event (OCR finished) and perform an action (tag the document,
>> move to the cabinet). The problem is that the triggers and actions are
>> static. You can't program any kind of intelligence in them. There is no
>> method to add a decision (what folder based on what OCR content). We have
>> been talking about solving this with what we called workflow filters. The
>> specs are still in design phase as we don't want to create a whole separate
>> programming language for this. Eric is particularly interested in this
>> still (we wants to auto tag documents based on OCR content) so this will
>> get done as soon as we figure out the design.
>>
>> On Tuesday, March 20, 2018 at 9:13:22 AM UTC-4, Raul wrote:
>>>
>>> Hi guys,
>>>
>>> I am pretty new to Mayan EDMS.
>>> So far I have been only testing on how to install it and what hardware
>>> would be a good match for it.
>>>
>>> I am not at a state where I have installed EDMS 3.0 and am wondering
>>> about the following:
>>>
>>> 1.) How can I create an index of the year, month of the document date
>>> itself?
>>> 2.) How can I set the document title so that it builds it out of for
>>> example invoice number, date and company?
>>> 3.) How can I create a trigger that automatically assigns tags to
>>> documents and adds them to a special cabinet? All outgoing from keywords
>>> that match with the OCR result.
>>>
>>> Thanks for your help :)
>>>
>> --
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Mayan EDMS" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/mayan-edms/ONBovsdTKfI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mayan-edms+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Mayan EDMS: 2406] Re: Announcing Mayan EDMS NG version 2.8

[Michael Price]

Do a

docker logs 

it should say why it is restarting.

On Sun, Apr 1, 2018 at 7:59 AM, Jos vd Snepscheut  wrote:

> Hello,
>
> I 'm trying to run Mayam EDMS NG 3.0.2 (and 3.0.1) both by using the
> docker image and by buildinging it according your instructions.
> But unfortunatly all my containers keeps restarting.
> What am I doing wrong?
> Where can i find help?
>
> Thanks,
>
> Jos.
>
> Op dinsdag 27 februari 2018 11:40:20 UTC+1 schreef Michael Price:
>
>> Hi all,
>>
>> We love Mayan EDMS and have come to depend on it for our daily work. Like
>> many of you we are worried about the effects hurricane Maria has had on the
>> development of the project. So we decided to do something about it.
>>
>> We gained good knowledge about the internals of Mayan EDMS from customizing
>> it for our own use. Looking at the code for the next version we could see
>> that much work had already been done. We were confident we could finish the
>> remainder tasks to be able to take the code to a point where a version 2.8
>> would be possible.
>>
>> We contacted Roberto with our idea. While his communication options are
>> limited, he nonetheless provided us with some great guidelines. We don't
>> pretend our fork to replace Mayan EDMS so we are naming it Mayan EDMS NG
>> (Next generation). To make things easier we continued the version
>> numbering.
>>
>> So, we are proud to release our work as Mayan EDMS NG version 2.8.
>>
>> Our forks is just a continuation of the work already started by Roberto
>> for version 2.8. Therefore it is 100% compatible with any existing data.
>>
>> Our work focused on the following areas:
>>
>> * Finishing the API test refactor. The purpose of this refactor is to
>> test each API function for permission and access failure and success. The
>> API tests we also updated to conform with the new API Test class interface
>> which reduces a lot of boilerplate code. There are now a minimal of two
>> tests for each API function.
>>
>> * Some minor permission changes were made when obviously needed such as
>> the Workflow Create permission not having any effect.
>>
>> * Roberto had already backported the notifications feature to the "next"
>> branch and our work just focused on giving the final polish to this feature
>> by removing duplication.
>>
>> * Some user interface fixes and updated we added. These were inspired by
>> discussion on the mailing list and from looking at the Open Paperless fork
>> by Tina Zhou.
>>
>> * Introduction of the MERC (Mayan EDMS Request for Comment) as a means of
>> documenting the internals of the project, proposing features, changes to
>> the code as well as to the related process of the project. This type of
>> documentation mechanism has been very successful for other things like the
>> Internet (RFCs), Python (PEPs) and Django (DEPs) and we are sure it will
>> also help Mayan EDMS a lot.
>>
>> The repository for this fork is https://gitlab.com/Michael.
>> Price/mayan-edms. From there you can examine the changes that we made to
>> get the code to release level. Our work is available from PyPI as
>> mayan-edms-ng.
>>
>> We hope you enjoy it, thank you.
>>
>> Michael Price, internals and process
>> Eric Riggs, user interface
>>
> --
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Mayan EDMS" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/mayan-edms/Fx8rz4kxPCw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mayan-edms+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Mayan EDMS: 2405] Re: Ever wished there was a professional version of Mayan EDMS?

[Michael Price]

Dunno. I don't have administrative access to view the settings of the
mailing list. Roberto might be able to answer this.

On Fri, Mar 30, 2018 at 3:43 AM, Costi Budai  wrote:

> Hmmm, any idea why my message disappeared? "This message has been deleted.
> "
>
> On Wednesday, March 28, 2018 at 10:00:33 PM UTC+3, Michael Price wrote:
>
>> See what we've been up to. Many of your requests answered.
>>
>> https://medium.com/@loneviking72/ever-wished-there-was-a-
>> professional-version-of-mayan-edms-7c9d49425cca
>>
> --
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Mayan EDMS" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/mayan-edms/Kd3NuZHZtwQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mayan-edms+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2405] Upgrading from 2.7.3 to NG Versions

[David Kornahrens]

Hello community,
We are currently on 2.7.3, deployed through Docker.  I am interested in 
updating to the latest NG version, if it's supported to upgrade through 
Docker.

The only concern, we deployed Django Storages and offload media to Amazon 
S3.  We need to ensure this stays offloaded to S3 and that our documents 
can still be viewed when updated.  We currently have ~5K files.

Is this able to be upgraded via Docker?  Or do we need to wait for official 
support from the Mayan repository?

Thanks,
David

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2404] Re: Situation update

[David Kornahrens]

Glad to hear you are doing well, considering.  Look forward to you getting 
100% back on your feet.

On Saturday, March 31, 2018 at 2:41:49 AM UTC-4, Roberto Rosario wrote:
>
> Big thank you to everybody that has reached out, sent first necessity 
> items, and donated. You have made a situation without precedent much more 
> bearable. 
>
> This is the situation at the moment (without going into politics or 
> corruption, that has gone to a whole new level of insanity).
>
> Utilities are mostly working. There are still a several outages per week 
> but in comparison with having no power, it is a much better situation. Now 
> we can purchase groceries knowing the chances of it spoiling are much 
> lower. 
>
> Internet and cell phone service are still spotty. We get 1Mbit of download 
> speed. Using heavy ad filtering and compression browsing experience is 
> tolerable but trying to watch streaming content is painful. The same goes 
> for VOIP and video calls. Remote work takes patience.
>
> Driving around is still an adventure. A lot of traffic lights are still 
> out. Intersections are like a gauntlet. Patience in the streets is low and 
> people are very prone to road rage. Traffic jams last hours. In those 
> situations phone navigation is useless as there are still many connectivity 
> dark zones.
>
> Like most people in the island, my income sources have been gravely 
> affected. Spending now the same amount of time I used to spend on Mayan and 
> my other free projects is a luxury I can't afford. I hope to be able to 
> take some time soon to revise all the work done by the Mayan EDMS NG team 
> and start merging. Since their fork has moved quite a bit ahead of Mayan 
> EDMS, this revision and merge process will be mostly manual. To make the 
> most of the time, I'll focus on bug fixes and outdated version updates 
> (Django, packages, etc), before going into features. From what I've seen so 
> far, they have done a very good job. Their job quality will make mine 
> easier.
>
> This has been the worst natural disaster in generations and one of the 
> worse experiences I've had to go through. But we survived it and that's all 
> that matters. We rebuilt our island. And we will rebuild this, our project.
>
> Thank again to everybody.
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2403] Re: Document date and title

[Raul]

Hi Michael,

thanks for your response.
I finally got my server in place and am ready to rock now.

Regarding my questions:

1) I was more thinking about something like it is done in paperless 
(https://github.com/danielquinn/paperless).
Here the date is being extracted out of the OCR content and used as 
document date. Which is a very nice feature.

2) You are right the addon is outdated.

3) That would be definitely nice. I the way it is right now the OCR content 
is only used for searching. However, there could be so much more you could 
do with it. Like search for keywords and trigger the auto assign to a 
cabinet or get the document date etc

Am Freitag, 23. März 2018 06:25:11 UTC+1 schrieb Michael Price:
>
> Hi,
>
> How are you liking version 3.0?
>
> Here are the answer to your questions.
> 1. The file creation data is lost during the upload. These operating 
> system fields and do not persist during upload via web. It could be 
> possible to retain these values if the document is uploaded via a watch 
> folder or staging folder. Since these methods open the file to be loaded 
> into Mayan directly from the operating system the file creation could be 
> read.
>
> 2. It is not possible using the normal installation. However I found this 
> online: https://gitlab.com/mayan-edms/document_renaming it seems to do 
> what you want. Haven't tried it and looks outdated. If there is enough 
> interest we could add something like this in our fork of Mayan.
>
> 3. Not yet possible at the level you want right now but it is getting 
> there. There is a workflow feature called triggers and another called 
> actions. These allow you to create a workflow that will respond (trigger) 
> based on an event (OCR finished) and perform an action (tag the document, 
> move to the cabinet). The problem is that the triggers and actions are 
> static. You can't program any kind of intelligence in them. There is no 
> method to add a decision (what folder based on what OCR content). We have 
> been talking about solving this with what we called workflow filters. The 
> specs are still in design phase as we don't want to create a whole separate 
> programming language for this. Eric is particularly interested in this 
> still (we wants to auto tag documents based on OCR content) so this will 
> get done as soon as we figure out the design.
>
> On Tuesday, March 20, 2018 at 9:13:22 AM UTC-4, Raul wrote:
>>
>> Hi guys,
>>
>> I am pretty new to Mayan EDMS.
>> So far I have been only testing on how to install it and what hardware 
>> would be a good match for it.
>>
>> I am not at a state where I have installed EDMS 3.0 and am wondering 
>> about the following:
>>
>> 1.) How can I create an index of the year, month of the document date 
>> itself?
>> 2.) How can I set the document title so that it builds it out of for 
>> example invoice number, date and company?
>> 3.) How can I create a trigger that automatically assigns tags to 
>> documents and adds them to a special cabinet? All outgoing from keywords 
>> that match with the OCR result.
>>
>> Thanks for your help :)
>>
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2402] Re: Announcing Mayan EDMS NG version 2.8

[Jos vd Snepscheut]

Hello,

I 'm trying to run Mayam EDMS NG 3.0.2 (and 3.0.1) both by using the docker 
image and by buildinging it according your instructions.
But unfortunatly all my containers keeps restarting.
What am I doing wrong?
Where can i find help?

Thanks,

Jos.

Op dinsdag 27 februari 2018 11:40:20 UTC+1 schreef Michael Price:
>
> Hi all,
>
> We love Mayan EDMS and have come to depend on it for our daily work. Like 
> many of you we are worried about the effects hurricane Maria has had on the 
> development of the project. So we decided to do something about it.
>
> We gained good knowledge about the internals of Mayan EDMS from customizing 
> it for our own use. Looking at the code for the next version we could see 
> that much work had already been done. We were confident we could finish the 
> remainder tasks to be able to take the code to a point where a version 2.8 
> would be possible.
>
> We contacted Roberto with our idea. While his communication options are 
> limited, he nonetheless provided us with some great guidelines. We don't 
> pretend our fork to replace Mayan EDMS so we are naming it Mayan EDMS NG 
> (Next generation). To make things easier we continued the version 
> numbering. 
>
> So, we are proud to release our work as Mayan EDMS NG version 2.8.
>
> Our forks is just a continuation of the work already started by Roberto 
> for version 2.8. Therefore it is 100% compatible with any existing data. 
>
> Our work focused on the following areas:
>
> * Finishing the API test refactor. The purpose of this refactor is to test 
> each API function for permission and access failure and success. The API 
> tests we also updated to conform with the new API Test class interface 
> which reduces a lot of boilerplate code. There are now a minimal of two 
> tests for each API function.
>
> * Some minor permission changes were made when obviously needed such as 
> the Workflow Create permission not having any effect.
>
> * Roberto had already backported the notifications feature to the "next" 
> branch and our work just focused on giving the final polish to this feature 
> by removing duplication.
>
> * Some user interface fixes and updated we added. These were inspired by 
> discussion on the mailing list and from looking at the Open Paperless fork 
> by Tina Zhou.
>
> * Introduction of the MERC (Mayan EDMS Request for Comment) as a means of 
> documenting the internals of the project, proposing features, changes to 
> the code as well as to the related process of the project. This type of 
> documentation mechanism has been very successful for other things like the 
> Internet (RFCs), Python (PEPs) and Django (DEPs) and we are sure it will 
> also help Mayan EDMS a lot.
>
> The repository for this fork is 
> https://gitlab.com/Michael.Price/mayan-edms. From there you can examine 
> the changes that we made to get the code to release level. Our work is 
> available from PyPI as mayan-edms-ng.
>
> We hope you enjoy it, thank you.
>
> Michael Price, internals and process
> Eric Riggs, user interface
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.