Skip to content

Remove RelatedRecords, AssociatedResources & IncomingRelations

Rod Scott requested to merge EMC-106-related-records into develop

Important

Please review and approve this merge request only. Data will need to be migrated from 'relatedRecords' to 'relationships' so need to plan how this is deployed to production.

Work Done

Multiple conflicting ways have been implemented to store relationships between documents. This merge request simplifies all those different ways into one way of dealing with them, Relationships.

CodeDocument, ElterDocument, GeminiDocument and InfrastructureRecord were the document types with RelatedRecords that have been removed. RelatedRecord and the properties on ElterDocument and GeminiDocument will be removed after data migration.

GeminiDocumentPostProcessingService has had Jena querying functionality removed and moved to the JenaLookupService where all the Jena querying is done for the Freemarker templates.

The relatedRecord indexing has been removed from the Jena indexing classes.

Freemarker templates modified to use JenaLookupService to get links.

Javascript editors updated to replace RelatedRecordView with RelationshipView.

Other Work

MapServerIndexingService has had the exec method upgraded and the single Sting method was deprecated, an array of Stings was needed instead. The test for this has broken so I have disabled it, I'm not sure the test was actually doing what we thought. I think in a new process it doesn't have permission to see the JUnit temp directory.

EMC-106

Merge request reports

Loading