• V2Issues

V2, MAPS and Infrastructure - Design and Implementation Issues

V2Master

• Contents

  1. V2, MAPS and Infrastructure - Design and Implementation Issues
  2. Introduction
  3. V2 Issues
     1. V2 Design Issues
        1. Documents, Revisions and Folders
     2. V2 Implementation Issues
        1. Using DISTINCT on Search SQL (Status: undecided)
  4. MAPS Issues
  5. Infrastructure Issues
     1. Vagrant File Share Performance

Introduction

Includes issues associated with:

1. V2
2. MAPS
3. Infrastructure

V2 Issues

V2 Design Issues

Documents, Revisions and Folders

How design the access rights for documents and revisions.

Assumptions:

1. Customers are likely to understand folders as a means of controlling who can view and update documents and revisions

Long-Term requirements:

1. It should be possible to hide documents from certain users
2. It should be possible to hide specific revisions from certain users
   1. Because the latest revision is not complete or not yet issued
   2. Because an intermediate revision is not issued

Issues:

1. If a revision belongs to a folder and a document not:
   • - How are updates to its document recode, the document code and classifications, controlled?

     - Every user who has in any folder update permission will have the possibility to create a version to every document where the user can read any of its revision.

2. If a document belongs to a folder and its revisions can belong to different folders:

   • - Every user who has in any folder update permission will have the possibility to create a version to every document the user can read.

3. If a document belongs to a folder, including all its revisions, how can you hide/show specific revisions?

Ideas:

1. Have a 'hidden flag' in revisions and an extra read role that allows viewing of hidden revisions
   1. The normal view role would not show hidden revisions
   2. Update role would include the ability to view hidden revisions

Suggested implementation

1. For now, implement a folder_id in documents, folder_id in revisions and file_assets will be synchronized with the associated document for performance reasons, first of all in the authorization. No hidden flag.

V2 Implementation Issues

Using DISTINCT on Search SQL (Status: undecided)

Issue:

• If documents/revisions/tasks are sorted by a classification class, in which an object has more than one classification,

  then the object appears on the list more than once if we do not use the DISTINCT SQL keyword. E.g.:

   SELECT DISTINCT revisions.* FROM `revisions` INNER JOIN ...

  But if we are using the DISTINCT SQL keyword than the sorting doesn't seems to be correct, because the sorting is effective after the distinct filtering.

Suggested implementation:

• We should use the DISTINCT SQL keyword and to display a warning if potentially some records are displayed many times.

• The warning could be, e.g.: "WARNING: Revisions with more than one Location value will appear more than one time in the list".

MAPS Issues

Infrastructure Issues

Vagrant File Share Performance

1. There are potential performance issues with native Vagrant share_folder

   1. Vagrant document suggests using NFS shares instead
   2. We should do performance tests of document access and backups

   3. See: http://docs-v1.vagrantup.com/v1/docs/nfs.html

2. Vagrant share_folder suffers from a VirtualBox bug

   1. Work around is to set Apache config option: EnableSendFile off

   2. See: https://github.com/mitchellh/vagrant/issues/351

3. Vagrant NFS share bug
   1. Symptom: During 'vagrant up' the following is displayed:
      1. /etc/init.d/nfs-kernel-server: command not found

   2. The problem is that a Ubuntu NFS restart command is being run on the CentOS host

   3. See: https://github.com/mitchellh/vagrant/issues/1394