[Mayan EDMS: 2015] Re: Upload wizard question
I second this request. Not fully understanding the index feature, cabinets is our best way to organize data. On Friday, August 11, 2017 at 10:56:46 AM UTC-4, LeVon Smoker wrote: > > Roberto, > > Is there a release target date for the document upload wizard refactor? > Specifically, I'm looking for the ability to add cabinets during upload. > > In the mean time, what's the best way to hack in cabinets on the upload > wizard? > > Thanks, > LeVon Smoker > -- --- 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: 2013] Upload wizard question
Roberto, Is there a release target date for the document upload wizard refactor? Specifically, I'm looking for the ability to add cabinets during upload. In the mean time, what's the best way to hack in cabinets on the upload wizard? Thanks, LeVon Smoker -- --- 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: 2013] Re: Limit number of OCR processes
Hi Roberto, thanks a lot for your support - works perfectly. Regards Mirco Am Freitag, 11. August 2017 03:26:36 UTC+2 schrieb Roberto Rosario: > > Hi, > > You can control the number of OCR processes using the "--concurrency=1" > setting of Celery on the worker managing the OCR queue. This causes Celery > to executye > > For example (from the Docker image): > > python /usr/local/lib/python2.7/dist-packages/mayan/bin/mayan-edms.py > celery --settings=mayan.settings.production worker -Ofair -l ERROR -Q > mailing,ocr,tools,statistics -n mayan-worker-slow.%%h --concurrency=1 > > If you are still running out of memory you can add the --concurrency=1 > setting to the other workers to control the conversion and display > processes. > > On Thursday, August 10, 2017 at 1:07:55 PM UTC-4, Mirco Hansen wrote: > >> Hi, >> >> is there a way to limit the number of OCR processes running at the same >> time? If I upload lots of documents the OCR in the background makes Mayan >> mostly unusable so I want to limit the number of background jobs. >> >> Thanks in advance. >> >> Regards >> Mirco >> >> -- --- 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: 2012] Rebuilding Files
Hi We have quite a lot of files that was scanned and processed at Grayscale, 300DPI with over 2000 pages. These files are large in size, with some over 2GB per file. Our clients has now decided that we can reduce the files in size and use a different compression algorithm. We now want to run our code on the files that are stored within Mayan. We can do this with ease, but the metadata about file size etc needs to be updated. How can we trigger an update on the metadata stored within Mayan on amount of pages, file size etc, about a file that already exists? We do not want to load a new version, but would like to update the current version. -- --- 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: 2009] Re: docker local.py settings import error
this is my local.py: from __future__ import absolute_import from .base import * SECRET_KEY = 'foo' On Friday, August 11, 2017 at 9:11:11 AM UTC+2, Tony Nys wrote: > > Thanks Roberto , but i still have the same issue: > now I do this > docker volume create --name mayan_media --opt type=none --opt > device=/Users/tony/mayan_data --opt o=bind > docker volume create --name mayan_settings --opt type=none --opt > device=/Users/tony/mayan_data --opt o=bind > docker run --env-file=/Users/tony/mayanlocalpostgres.properties --name > mayanedmspostgresql -p 80:80 -v mayan_media:/var/lib/mayan -v > mayan_settings:/etc/mayan mayanedms/mayanedms > > still same error: > > mayan.settings <217> [ERROR] "() Error importing user's local.py; > No module named media.settings.local" > > On Friday, August 11, 2017 at 7:47:51 AM UTC+2, Tony Nys wrote: >> >> as I see, the mounted docker folder eg. mayan_data, needs a subfolder >> "settings". >> Mayan will check if a local.py file exist , and if not do an initial >> installation and create a local.py file in that folder >> >> But when I start mayan the 2nd time, so the file exists, it gives the >> error >> >> mayan.settings <208> [ERROR] "() Error importing user's local.py; >> No module named media.settings.local" >> >> so my local.py is in /Users/tony/mayan_data/settings >> >> Starting docker: >> >> docker run --name mayanedmspostgresql -p 80:80 -v >> /Users/tony/mayan_data/:/var/lib/mayan mayanedms/mayanedms >> >> >> >> -- --- 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: 2008] Re: Cannot Rebuild Indexes manually (MultipleObjectsReturned)
Ah yes! Didn't saw it, thanks! On Friday, August 11, 2017 at 2:30:44 AM UTC-4, Gerrit Van Dyk wrote: > > The line number is from lock_manager/managers.py in check_existing on line > 55. > > I am running this from the normal Rebuild Indexes on the Tools menu. > > On Friday, August 11, 2017 at 3:52:25 AM UTC+2, Roberto Rosario wrote: >> >> "get() returned more than one Lock -- it returned 15!" <- That should >> not be happening. >> >> Can you share the index template you used that triggers this or a >> simplified version with no private information? >> >> The locks should be releasing even on errors ( >> https://gitlab.com/mayan-edms/mayan-edms/blob/master/mayan/apps/document_indexing/models.py#L271 >> ). >> >> What line number is the .get() error happening? >> >> In the worst case, lock have a default timeout of 30 seconds ( >> https://gitlab.com/mayan-edms/mayan-edms/blob/master/mayan/apps/lock_manager/settings.py#L19 >> ) >> >> While the cause of the issue in found and fixed you can force a release >> of all lock with the management command (command line): >> >> ./manage.py purgelocks >> >> To achieve the same from code (from Python) use: >> >> from lock_manager.runtime import locking_backend >> locking_backend.purge_locks() >> >> >> On Thursday, August 10, 2017 at 10:18:02 AM UTC-4, Gerrit Van Dyk wrote: >>> >>> Hi, >>> >>> When trying to rebuild all indexes, I get the following error. >>> >>> Exception Type: MultipleObjectsReturned, Exception Value:get() returned >>> more than one Lock -- it returned 15! >>> >>> It seems that this error is coming from lock_manager/managers.py in >>> check_existing on line 55. >>> >>> existing_lock = self.get(**kwargs) >>> >>> >>> How can I clear these errors, or get rid of the multiple locks. >>> >>> >>> Gerrit >>> >>> >>> >>> >>> -- --- 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: 2007] Re: multi tenancy
A multi tenant branch was started some time ago to support this natively ( https://gitlab.com/mayan-edms/mayan-edms/commits/feature/multi-tenant). It implements an Organization class to handle each tenant's data. It is still not complete. The tests for the 300+ views are not yet finished. Feel free to work on it if you have the time. Until native database agnostic multi tenant is finished, a plugin that provides tenancy using database schemas is available in the app store: https://www.mayan-edms.com/store/ On Friday, August 11, 2017 at 2:37:04 AM UTC-4, Tony Nys wrote: > > Ideally in mayan, a concept/class Tenant should be there: where a Tenant > has > * Id > * Name > * External-ID (reference), Unique but optional : eg. the Syneton tenant id > * StorageCollection: container name used eg. in Azure/AWS/... or local > subfolder-name in the 'document_storage' folder > > A Group has a FK id to a Tenant > A documenttype has a FK id to a Tenant > A Cabinet has a FK id to a Tenant > > so the tenant is actually a group of groups > > > In a first phase, the FK could just be an optional attribute, > In a later phase, ACLs could be assigned to a Tenant, > > -- --- 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: 2006] mayan stateless cluster / docker swarm
I want to set up 2 mayan servers running the docker image Each server will be connected to the same database server (postgresql) and the same external blob storage (eg. Azure) WIll there be any issue/concern setting up such a cluster / docker-swarm ? -- --- 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: 2005] multi tenancy
Ideally in mayan, a concept/class Tenant should be there: where a Tenant has * Id * Name * External-ID (reference), Unique but optional : eg. the Syneton tenant id * StorageCollection: container name used eg. in Azure/AWS/... or local subfolder-name in the 'document_storage' folder A Group has a FK id to a Tenant A documenttype has a FK id to a Tenant A Cabinet has a FK id to a Tenant so the tenant is actually a group of groups In a first phase, the FK could just be an optional attribute, In a later phase, ACLs could be assigned to a Tenant, -- --- 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: 2004] Re: Cannot Rebuild Indexes manually (MultipleObjectsReturned)
The line number is from lock_manager/managers.py in check_existing on line 55. I am running this from the normal Rebuild Indexes on the Tools menu. On Friday, August 11, 2017 at 3:52:25 AM UTC+2, Roberto Rosario wrote: > > "get() returned more than one Lock -- it returned 15!" <- That should not > be happening. > > Can you share the index template you used that triggers this or a > simplified version with no private information? > > The locks should be releasing even on errors ( > https://gitlab.com/mayan-edms/mayan-edms/blob/master/mayan/apps/document_indexing/models.py#L271 > ). > > What line number is the .get() error happening? > > In the worst case, lock have a default timeout of 30 seconds ( > https://gitlab.com/mayan-edms/mayan-edms/blob/master/mayan/apps/lock_manager/settings.py#L19 > ) > > While the cause of the issue in found and fixed you can force a release of > all lock with the management command (command line): > > ./manage.py purgelocks > > To achieve the same from code (from Python) use: > > from lock_manager.runtime import locking_backend > locking_backend.purge_locks() > > > On Thursday, August 10, 2017 at 10:18:02 AM UTC-4, Gerrit Van Dyk wrote: >> >> Hi, >> >> When trying to rebuild all indexes, I get the following error. >> >> Exception Type: MultipleObjectsReturned, Exception Value:get() returned >> more than one Lock -- it returned 15! >> >> It seems that this error is coming from lock_manager/managers.py in >> check_existing on line 55. >> >> existing_lock = self.get(**kwargs) >> >> >> How can I clear these errors, or get rid of the multiple locks. >> >> >> Gerrit >> >> >> >> >> -- --- 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: 2003] Logging database and file storage performance
trying to set up mayan/django to an external Postgresql database and Azure blob storage It is working but it is slow Is there an easy way to set up benchmarks for * query response time * blob upload/download response time -- --- 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: 2002] Re: docker local.py settings import error
This is a problem cause by a design decision of Docker that initializes volumes in different ways depending on the type of volume: https://gitlab.com/mayan-edms/mayan-edms-docker/issues/6#note_22653707 Until Docker fixes this use only named volumes when deploying the Mayan Docker image. On Friday, August 11, 2017 at 1:47:51 AM UTC-4, Tony Nys wrote: > > as I see, the mounted docker folder eg. mayan_data, needs a subfolder > "settings". > Mayan will check if a local.py file exist , and if not do an initial > installation and create a local.py file in that folder > > But when I start mayan the 2nd time, so the file exists, it gives the error > > mayan.settings <208> [ERROR] "() Error importing user's local.py; > No module named media.settings.local" > > so my local.py is in /Users/tony/mayan_data/settings > > Starting docker: > > docker run --name mayanedmspostgresql -p 80:80 -v > /Users/tony/mayan_data/:/var/lib/mayan mayanedms/mayanedms > > > > -- --- 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.
