The view concept is at the very heart of the WIND. It allows you to create and manage any number of 'recordings' of actions, which are stored in identified working spaces called Views.
A view can therefore keep changes made to the Typed tree or to the File resources tree, changes made to existing documents and of course newly created documents.
- Managing views: allows you to use a given view to organize your work, create content and make all the necessary changes until the material is ready to be published.
- Displaying views: allows you to privately monitor how your changes would appear on the Portal, by generating a page mixing the actual NOP content and your own contribution.
Managing Views
As you initiate a WIND session and open the WIND Detail window to start working, this is how the header looks like:
The User field tells with which account you are logged in to the Portal, and the View field indicates the currently set view - by default, it will be the published view, containing all the elements and structure of the published NOP (in other words, the Portal as it is seen by the public).
The View Management Menu
By default, the View Management menu proposes the commands as shown above, with the Delete and the Publish current view command greyed out (not available) since, by default, there is nothing yet to delete or publish at this stage.
As soon as you start creating views, they are listed in the menu, and accessible for any further action:
The View Management allows you to create views, or perform various actions on the views created using the account with which you are logged in:
Create view ...
Note: A given user can only own 10 views. A warning pops up when you exceed the limit:
The view is created, and becomes the active one, as reflected in the header:
Another quick way to create a view is to select an entity (or group of entities) and make use of the contextual menu:
A new session will be automatically created and set for you, and named after your username appended with a time stamp (example: testUser_2022_02_15_18_07_07).
Transfer view ...
This enables you to select and Transfer a View from a given owner (the user with which the view was created) to another user.
The field labels are self-explanatory - simply fill in the form and click on the Transfer View button to execute the command.
Transferring a view can be very useful, as it allows you to:
- pass unfinished work to a colleague to resume,
- send your work for validation to a supervisor,
- unblock a situation where an absent user has left locked items which another user urgently needs to access.
Delete view ...
Select the desired view to remove from the drop down list ...
... then confirm in the pop-up dialog:
Validate current view
Click on the Validate current view command:
Upon successful validation, this dialog is presented, against a green overlay:
When errors are encountered, they are identified and listed in this other dialog, against a red overlay:
Publish current view
Click on the Publish current view command:
Confirm when prompted:
Upon successful validation, this dialog is presented, against a green overlay ...
... and the just published view is removed from the list, and the application switches to the Published view, which now contains the latest changes:
Published
The currently published view. It is managed by the system, and cannot be deleted.
Displaying Views
You may wish to monitor the progress on your work and check how your changes will look like in the Portal.
As a good practice, you will also want to give your changes a last look before publishing your work.
To do so, return to the header of the NOP and click on the View button:
This opens the View selector, from which you will set the view to display in the Portal:
For this example, we have selected for you the view MyFirstSavedView and clicked on the Set button. It is easy to check which is the view currently in use by clicking again on the View button in the header.
Continuing our example, this is how the View selector would now look like:
This tells you that the current view is indeed MyFirstSavedView - and enables you to either opt for another view, or revert to the published view and restore the Portal in its initial state.
This step is very important to perform a visual check of your data.