From RPM Wiki
| Table of contents |
Summary
Create identifiable locations for storing RPM data. In other words, a generic content management system.
Why build it
Currently all information in RPM has to be a form in a process or an agency or other structured business object. We don't have any simple, system wide information storage mechanisms.
This feature would allow us to replace various intranet or content management systems that customers may have in place. It can even replace shared folders/VPN systems they may be using. This is important since the more systems RPM can replace, the more attractive it becomes.
It is also important as we see the value proposition of RPM move more from a "commission calculator" to a "secure collaboration and data sharing tool". I think this shift is key for the oil industry.
Examples of use
- Product catalog
- Training information
- Safety documents
Low hanging fruit
This is a somewhat easy feature to develop since it doesn't involve views, importing, downloading, custom fields, etc.
Details
The definition of a library simply requires giving it a name, description, and permissions. It then becomes available for use.
Pages
If you picture each library as a process the structure is similar to process management without forms and without separate designer pages.
- Libraries - This is the main page. Similar to process management, on the left is a list of all libraries the user can see. On the right is "Add a library" if the user has "libraries.setup".
- Link from home page.
- Staff only. Agent users have libraries listed on the home page (like processes).
- Add/edit a library - One page wizard with a name text field and description text area. "Edit" is from info box.
- Add "OK" returns user to the new library. Add "Cancel" returns user to main "Libraries" page.
- Edit "OK" and "Cancel" both return to library details.
- Library details - This is the page where a user makes use of the contents of a library. It also serves as the launch for all setup-related links.
- If the user has "libraries.setup" the tools over shows library on/off control and "Edit security" link (like template).
- Tool bar shows "Delete", "Setup" links if the user has "libraries.setup". There are multiple web boxes displayed:
- "Info" - Name and description. "Edit" link shown if the user has "libraries.setup".
- "Notes" - Standard notes shared by all who can see the library. "Edit" link requires "Read & edit" library permission.
- Each component (see below).
- Setup a library - A grid that lists the components in a library. The tool bar has an "Add" link. Each row in the grid shows the "Name", "Type", and "Content" columns as well as a "Delete" column (goes to recycle bin). Sorted alphabetically by name.
- The content field will show a file attachment count for attachment components. Example: "4 files"
- Add a component - One page wizard with a Name field. In the future it will include a component type selector.
- Edit library security - Similar to the template security page. One page wizard with drop downs to select library access per role and user type.
Components
The library designer manages library components. Components show up as web boxes on the library details page. For the first version of this feature we'll just have one type:
- Attachments - By adding multiple components the user is adding categories of files. Each one has a name that shows up as the web box title.
- "Edit" link requires "Read & edit" library permission.
Security
- "Library setup" privilege for staff allows library add, setup, and delete.
- Per library on/off control (like for processes)
- Default for new library is "Off"
- Per library per role as well as for "Agent users":
- "Hidden", "Read only", and "Read & edit" for the library by user type and role.
- Default for new library is "Read & edit" for each staff role and "Hidden" for agent users.
- Each file attachment still has the same "Hidden for agent users" option inherent to file attachments.
- Security groups:
- Libraries
- Library (id)
- Setup
- Libraries
Other
- Deleted libraries go to the recycle bin.
Future improvements
- Custom field components. Not sure yet how this would look.
- Reference from forms and views?
- Inventories
Example
I want to have safety training information for my employees available through their RPM logon.
- I create a "Safety training" library
- I upload some training files and create a "checklist" inventory for this library so I can add training steps.
- Users now logon and see a "Safety training" link in the library section (or maybe home page). They click on it and see a collection of files and information for safety training.
- This page was last modified 15:18, 8 May 2009.
- This page has been accessed 2818 times.