Structure and restructure content (maintenance)

Wish - Structure and restructure content (maintenance)

Problem: The larger the repository's content, the harder it is to maintain, find what you are looking for, or get an overview of what content is available/has been created.

Why? Create (more) value by keeping consistency in the quality of BlueDolphin's repository while the need is changing or evolving within the organization

What:

In terms of repository maintenance we should be able to:

restructure fields and change fieldnames without that having a(n) (direct) impact on the repository;
move questionairs fields between questionairs;
have access to standard maintenance reports (to get insights on use, ánd inconsistencies) (reflection towards the base convention model)

Generally it would be valuable to see who is using the application (last-login)

Structure and restructure content (maintenance)

Comments

Didn't find what you were looking for?