• RE: .net upload api

    Not a problem.

    You are probably right about dialogs knowing what is hidden -- that is handy!

    Thanks,
    Joe Kaufman
  • RE: .net upload api

    Raymond,

    Just remember that dialog fields are not the same as the document (file cabinet) fields. A dialog might be configured to only show a subset of the fields, so it is only by looking at the document itself that you can know what the full structure is.

    Many layers of complexity!

    Thanks,

    Joe Kaufman

  • RE: .net upload api

    Raymond,

    As far as I know, fields/indexing is all done at the Document level, not the FileCabinet level (all of my counts are zero, too, even when iterating over the List).

    If you do something like this:
     
    DocumentsQueryResult docs = conn.GetAllDocuments(cabID);
    Document doc = docs.Items[0];
    int fieldCount = doc.Fields.Count;
    

    You will see the fields of the document, therefore from the cabinet definition.

    Thanks,
    Joe Kaufman




     
  • RE: .net upload api

    Raymond,

    I have three packages installed:

    DocuWare.RestClient
    DocuWarePlatformApi
    DocuWarePlatformApiCore

    DocwareWebclientIntegration is more for URL integration, which I implement by simply including the assembly "DocuWare.WebIntegration.dll" in my .NET project as a direct reference. The namespace you should be using in your code is "DocuWare.Platform.ServerClient". The WebClient and Platform are two separate things, and the Platform SDK stuff is all a part of "Platform".

    Thanks,
    Joe Kaufman
     
  • RE: .net upload api

    Raymond,

    It looks like you don't have the extension methods for the FileCabinet object (of which UploadDocument is one).

    Did you install all the proper NuGet packages so that your .NET solution has the DocuWare assemblies? That is where the extension methods reside, namely:
     
    ​​​​​​​​​​​​​​namespace DocuWare.Platform.ServerClient
    {
        public static class FileCabinetExtensions
        {
            public static Document AddDocumentSections(this Document document, params FileInfo[] file);
            public static Task<DeserializedHttpResponse<Document>> AddDocumentSectionsAsync(this Document document, params FileInfo[] file);
            public static Section ChunkAddSection(this Document document, FileInfo file, int chunkSize = 0);
            public static ImportResult ChunkImportArchive(this FileCabinet fileCabinet, FileInfo file, ImportSettings importSettings);
            public static ImportResult ChunkSynchronize(this FileCabinet fileCabinet, FileInfo file, SynchronizationSettings synchronizationSettings);
            public static Document ChunkUploadDocument(this FileCabinet fileCabinet, FileInfo[] files, int chunkSize = 0);
            public static Document ChunkUploadDocument(this DialogInfo dialog, Document document, FileInfo[] files, int chunkSize = 0);
            public static Document ChunkUploadDocument(this DialogInfo dialog, Document document, FileInfo file, int chunkSize = 0);
            public static Document ChunkUploadDocument(this FileCabinet fileCabinet, Document document, FileInfo[] files, int chunkSize = 0);
            public static Document ChunkUploadDocument(this FileCabinet fileCabinet, Document document, FileInfo file, int chunkSize = 0);
            public static Document ChunkUploadDocument(this FileCabinet fileCabinet, FileInfo file, int chunkSize = 0);
            public static Section ChunkUploadSection(this Section section, FileInfo file, int chunkSize = 0);
            public static ImportResult ImportArchive(this FileCabinet fileCabinet, FileInfo file);
            public static ImportResult ImportArchive(this FileCabinet fileCabinet, FileInfo file, ImportSettings settings);
            public static ImportResult Synchronize(this FileCabinet fileCabinet, FileInfo file, SynchronizationSettings settings);
            public static Document UploadDocument(this FileCabinet fileCabinet, params FileInfo[] file);
            public static Document UploadDocument(this DialogInfo dialog, Document document, params FileInfo[] file);
            public static Document UploadDocument(this FileCabinet fileCabinet, Document document, params FileInfo[] file);
            public static Task<DeserializedHttpResponse<Document>> UploadDocumentAsync(this DialogInfo dialog, Document document, params FileInfo[] file);
            public static Task<DeserializedHttpResponse<Document>> UploadDocumentAsync(this FileCabinet fileCabinet, params FileInfo[] file);
            public static Task<DeserializedHttpResponse<Document>> UploadDocumentAsync(this FileCabinet fileCabinet, Document document, params FileInfo[] file);
            public static Task<DeserializedHttpResponse<Section>> UploadSectionAsync(this Document document, FileInfo file);
        }
    }
    

    Make sure the DocuWare NuGet packages are installed, rebuild your solution, and try again.

    Good luck!
    JoeK
  • RE: Full Text only done in first 100 pages of each doc

    I see now the max number of shots is 10,000, so that is what I am using.

    As far as resetting the full-text information, I click the "Reset" button and just use the defaults on the screen that comes up. It seems to be reindexing a lot of documents, so I think it is re-processing things appropriately.

    Thanks,

    Joe Kaufman

  • RE: Full Text only done in first 100 pages of each doc

    Josef,

    OK, so viewing the document skews the results, which is what I was afraid of...

    So, if I up the number of pages for all full-text indexed cabinets, I have the following questions:
     
    1. How high should (can) I go? can I go 999999, for example?
    2. How do I trigger a rescan of the text shots after I up the limit?
    3. Is this going to bloat textshot data in the database and cause me storage issues? (And I mean beyond the obvious growth due to documents with more than 200 pages having more pages getting processed.)
    Looks like I need to fix up a bunch of file cabinet configurations!

    Thanks,
    Joe Kaufman
  • RE: Full Text only done in first 100 pages of each doc

    Simon,

    I did some further testing...

    I found a file with 274 pages and picked one of those sticker-based numbers, slightly atilt, on page 121. Should be in between the first 100 and last 100 pages. I did a search while viewing the document, and it found the number on page 121.

    Then I thought that perhaps searching for text while viewing forces DocuWare to do a quick full-text scan of ALL pages. So, I found another file with 240 pages, and just viewed a number to search for on page 103. Went back and reset the search, then searched for the number in the "Fulltext" field. It found the document and went straight to page 103 in the viewer.

    Unless DocuWare immediately full-text scans any file that gets viewed, it looks like I have full coverage of all pages, not just the first and last 100, even though our default max. number of shots is still at 100. This is good news (for me), but I can't explain why other folks are stuck at the 100-page limit. I am on DW 6.11, on-premise.

    Thanks,
    Joe Kaufman

     
  • RE: Full Text only done in first 100 pages of each doc

    Josef,

    I am a little confused by the 100-page limit... Our setup looks to be at the default 100 "shots", which the help states is equivalent to 100 pages (one shot per page). But I just ran a full text search on a very specific number of our Production file cabinet (it is a sticker they stick on a batch sheet, and DocuWare does a good job of OCRing them), and it came right up with the single document in the cabinet, moving me straight to the page where the sticker was -- page 205 out of 212.

    How am I finding text on page 205 if the text shots are stopping after 100 pages? Or is the 100-page limit only for an initial shot-take? Does it run a longer full-text analysis later and get everything indexed?

    I never knew about this, but am now concerned, since we have full-text turned on for several file cabinets where the documents are over 100 pages...

    Thanks,
    Joe Kaufman
  • RE: Increasing Bar Code Recognition in v7 and above

    Kim,

    Just to make sure folks aren't put off by the idea of single-character barcodes, I'd like to reiterate they work fine across the board as long as devices are configured for it. In DocuWare it is the setting described above, and for some barcode readers you may need to talk to support and get a special setting configured. I bought a Nadamoo USB barcode reader and had to email them about it. Overnight they sent me a system barcode I could print out and scan, and now the gun reads single-character barcodes (numeric or alphabetic) perfectly.

    In any other scenario it is the fault of how the barcodes are being generated and/or the printer printing them. We use standard Code128 across the board, and I can read every barcode with my iPhone (no special changes needed), Android tablet (no special changes needed), Motorola industrial handheld computer (no special changes needed), USB scan gun (system barcode required), and DocuWare scanner (VintaSoft settings change).

    I guess I would say single-character barcodes aren't just possible, they should be the norm. If it won't scan with RedLaser on an iPhone, the barcode itself is malformed and nothing will read it. Are they best to avoid or work around? Maybe, but that's not always possible. Even barcoding something like a first name means some folks will just have a single character there, e.g. just the initial.

    Workarounds that work are wonderful though.  *smile*

    Thanks,
    Joe Kaufman