This content has been marked as final. Show 3 replies
Suggest that you make the documentation asset its own type, and create a relationship between it and the asset. This may cause one level of indirection between the asset and its doc (as the doc will not be an associated file.
The doc can be refernced by many assets this way, and the navigator is in essence the visual impact analysis report.
Oracle does publish the OER db schema for those who want to create custom reports.
I think you can get it through support.
This is exactly what we are doing for some of our project documentation. Some of our documentation itself is governed and OER is a great way to record the review Process at the various Governance Checkpoints. By creating an Asset Type for each (different) document type then you can create the relevant tabs etc also to record such information.
Then when you click on a Project you can see all the relevant artefacts for that project (including project docs and the results of their review process and where they are in their current lifecycle).