Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Target release

Epic

https://mydgict.atlassian.net/browse/HPD-301

/Document status

DRAFT

Document owner

Raoul Huisman

Designer

Tech lead

Arnaud Dusseldorp

Technical writers

@ writers

QA

🎯 Objective

Solution for importing multiple files in one time using a ZIP file.

\uD83D\uDCCA Success metrics

Goal

Metric

Simplify uploading multiple documents

Upload speed is increasing

Upload compliance documents and set directly the activity status and new planned date

Handling of compliance activities will speed up

\uD83E\uDD14 Assumptions

  • An existing HUMBLE User must upload the ZIP file

  • The import uses a queuing mechanism so it will be running asynchronous

\uD83C\uDF1F Brief description

A HUMBLE user must be able to upload a ZIP File that contains a set of files to import at once.

There are two possible ways:

  1. simple ZIP with or without a directory structure

  2. with a file which describes the filenames and the relations to entities in HUMBLE (like asset, building)

When there is no existing filename (description.csv), the importer acts the simple way (bullet 1). When the description.csv is in the ZIP it will use theses descriptions to import and link the documents

Simple ZIP

The files in the ZIP are all uploaded to HUMBLE and related to the given location. The document tab-page has a new button called upload ZIP

When the ZIP file contains a directory structure the importer will create a Tag for each directory. When a directory has sub-directories it will create one tag for the combination of directory and subdirectories divided by a '/' character

The tag is related to the document.

Example ZIP Structure

- Dak
  File1.pdf
  - Dak links
  File Dak links.pdf
  - Dak Rechts
  File Dak rechts.pdf
- Plattegrond
  Plat1.pdf
  Plat2.pdf

Creates

  • Tags

    • Dak

    • Dak / Dak Links

    • Dak / Dak Rechts

    • Plattegrond

With description file

The ZIP file must contain a file called ‘description.csv’ with a layout defined below

Layout columns:

  • Filename - Name of the file

  • Resource - relation to the HUMBLE entity

  • Id - Humble ID for the related record

  • Code - Unique code of the related record

  • Description - Description for the document

  • Status - Status for the document

  • Warning days - Number of days for pre-warning

  • Supplier - Reference to supplier

  • Tags - Diveded by ';'

  • Remark - Remark for a document

  • Document Date - Date of document (used for specific entities)

  • Compliance Set Code -

  • Compliance Rule Code - Rule code for the

  • Customfields - bij system_label

Filename

Model

Code

Tags

DocumentDate

RuleSet

1006400.pdf

location/floor

V-00000D00

Plattegrond

1006400.pdf

location/building

G-00000001

Algemeen;Contract

1006400.pdf

asset

0002999

18/09/2020

1007930.pdf

complianceactivity

0003000

12/01/2018

\uD83C\uDFA8 User interaction and design

Just an extra button on the document tab page

(question) Open Questions

Question

Answer

Date Answered

(warning) Out of Scope

  • No labels