This article stream is devoted to the support and training of all people interested in building and supporting CMS web sites, including extranets and training portals. It is not specifically targetting experts web masters and Drupal users. With the collective input and feedback from community members and our audience, we intend to continually review our learnings, and apply new and innovative techniques and modules to enhance the site and its functionallity.
The Mission of the IT Web Design team is to share our knowledge, experience and learnings in the methods, tools and processes for designing and developing functional, stable and innovated CMS style web sites.
We started a series of recent articles on integrating a Document Catalogue with Document Control. Our Catalogue model might look simplistic, but Drupal provides a number of modules and methods to extend the functionality to cover the needs of most small to medium businesses. In the real world, public access to most of the Catalogue would be severely limited. Ours is open for the purposes of training and discussion. But how would we restrict access to documents with Drupal? How could we customize the Catalogue to limit access to documents, and even sub-catalogues based on user profiles?
One solution lies with the Drupal Content Access module, which provides methods for restricting user access to certain types of Drupal Content, based on content specific or user type rules.
With our new document control system in place, the best way to demonstrate its use and versatility is to populate the catalogue for practical purposes. Note that the DCS and Catalogue are intended to be a working, training model, and may be adapted in other ways with more rigorous requirements in other working situations.
As mentioned in our March Newsletter, we intend to systematically migrate existing site documents from the current registers and indexes into the new catalogue format. For this discussion, we will register all our NewsCorner objects into a single catalogue. These currently are listed (rather feebly) in an index table under our Publications Menu.
In our previous article on Building a Document Catalogue , we gave an overview of both the catalogue, the Drupal components and using control records to integrate the catalogue with a Document Control system model. Now we might have some fun and describe in more detail, the process for building a team catalogue and adding documents.
For our demonstration, we will use the Quality Team, and create a catalogue for their procedures. Then we will register and add a process document, in that order. Create a control record to register the document, tag it to add to the required catalogue/s, then link the document source page/file as well as a distribution document.
It seemed most appropriate that the document we register for this example is the DCS Registration Process.
The two fundamental building blocks for constructing a practical, dynamic and maintainable Document Catalogue in Drupal are Views and Control Records. By Views we mean instances of tables generated by the Drupal View module. The Control Records we refer to are created from a custom content page (appropriately named Record), which acts as a template allowing us to achieve the following objectives:
Meet our organisation's Document and Quality Management standards for document and record control.
Provide a consistent document entity for populating any number of linked Document Catalogues, in a consistent , managable and scaleable format.
There are other clever Drupal modules and methods we employ to make this ongoing project a fascinating exercise.
This is one of a series of articles on the subject of managing records and documents, in a cloud environment. Our approach at QualityHelp will be to provide a practical, progressive and interactive format to the articles, blog discussions and our evolving Document Control framework. You can get involved by reviewing the structure of the Control Records, Master Catalogue, Team Indexes and Document templates as we develop the framework and components. Then provide feedback and input - suggestions and constructive comments.
Participate in our site's Continuous Improvement objectives and become a contributor to the evolving design.
Recently I updated my blog on Web Design with a review I came across called the Top Ten Best Web Hosting Companies of 2013. I know the title sounds a bit presumptuous, but was worth some merit due to the thoroughness and scope of the content.
You need to login to read our blogs and other material, but I'd thought I'd share my personal views and experience when it comes to selecting web hosting companies.
One of the driving objectives for building this site was to demonstrate the power of applying continuous process improvement over time. The structure and content will likely transform significantly.
This essentially means the site and it's underlying infrastructure will continue to evolve.
We started a series of recent articles on integrating a Document Catalogue with Document Control. Our Catalogue model might look simplistic, but Drupal provides a number of modules and methods to extend the functionality to cover the needs of most small to medium businesses. In the real world, public access to most of the Catalogue would be severely limited. Ours is open for the purposes of training and discussion. But how would we restrict access to documents with Drupal? How could we customize the Catalogue to limit access to documents, and even sub-catalogues based on user profiles?
With our new document control system in place, the best way to demonstrate its use and versatility is to populate the catalogue for practical purposes. Note that the DCS and Catalogue are intended to be a working, training model, and may be adapted in other ways with more rigorous requirements in other working situations.
In our previous article on 
The two fundamental building blocks for constructing a practical, dynamic and maintainable Document Catalogue in Drupal are Views and Control Records. By Views we mean instances of tables generated by the Drupal View module. The Control Records we refer to are created from a custom content page (appropriately named Record), which acts as a template allowing us to achieve the following objectives:
This is one of a series of articles on the subject of managing records and documents, in a cloud environment. Our approach at QualityHelp will be to provide a practical, progressive and interactive format to the articles, blog discussions and our evolving Document Control framework. You can get involved by reviewing the structure of the Control Records, Master Catalogue, Team Indexes and Document templates as we develop the framework and components. Then provide feedback and input - suggestions and constructive comments.
Recently I updated my blog on Web Design with a review I came across called the 
One of the driving objectives for building this site was to demonstrate the power of applying continuous process improvement over time. The structure and content will likely transform significantly.
Recent comments