* Roberto Rosario: " Re: [Mayan EDMS: 831] Mayan EDMS sprint at DjangoCon" (Fri, 5 Sep 2014 11:10:42 -0700 (PDT)):
> > > On Wednesday, September 3, 2014 6:47:05 AM UTC-4, Mathias Behrle wrote: > > > > * Roberto Rosario: " [Mayan EDMS: 811] Mayan EDMS sprint at DjangoCon" > > (Tue, 2 > > Sep 2014 15:08:02 -0700 (PDT)): > > > > > At DjangoCon there is interest in a Mayan EDMS sprint, wrote a sort post > > to > > > get the ball rolling http://blog.robertorosario.com/mayan-edms-sprint/. > > > > > Chime in with your thoughts, opinions and let's see if it is doable! > > > > Great to hear that. > > > > You already included workflow as topic, I would like to add a > > postprocessing > > queue and staging folders like proposed on [1]. > > > > Until now I got no feedback to the post [1], which may be caused by > > unclear > > statements. If so, please let me know to explain better. > > > > Indeed my proposal includes two steps: > > > > - workflow change: having document and OCR available on the metadata form > > to > > ease manual input and/or control. > > > > This relates to the new split screen document upload form? Yes. I am just repeating myself...;) > > - addition of a postprocessing document queue: a queue, that holds all > > documents included in the database and already processed by OCR, but > > lacking > > metadata (or with metadata to be controlled). > > > > Is this queue automatically populated when after OCR or is it populated > using the metadata delete signal and when the metadata count reaches 0? > Tagged this as issue #34. I would tend to make all this stuff configurable to be flexible: Configuration 1: Selection: - Include no documents after OCR (probably the default) - Include all documents after OCR - Include only those documents missing some metadata (configured in Configuration 2). Configuration 2: A list of metadata fields to be checked after OCR. If the metadata of the document are missing one of the configured fields, the document is added to the queue. > > Furthermore django 1.7 seems to be out and it is the target version for > > Debian > > next stable. To make packaging possible, this version would be required. I > > don't know about your feelings, but perhaps migration to 1.7 could be > > nice. > > > > > Opened issue #33 to track this. Looking at Django's relese notes to see > what needs to be updated in Mayan to make the jump. From what I read so far, changes in south migration could not be trivial. But I didn't dive deep enough into the topic until now to be of real help there. -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6
signature.asc
Description: PGP signature
