reqlanOverviewIdeasFilesCode filesClustersAttributesGraphPrint
Ideas/base_linking

Idea detail

base_linking

reqlan rq/bases/base.rq:99

block

Summary

A base may have one-directional relationships with other bases.
This follows a subscription model.
Bases may be cross subscribed.
Unless linked, than bases remain isolated.
Base linking is configured in the config file in the base. reqlan directory.
- an unlinked child base should sever the contained ideas from the parent base ( i. e. the parent should just see the child as a separate base and child ideas shouldn't be visible, the indexer shouldn't crawl it. ) they should be functionally distinct
- bases, distinct from eachother in the system file tree, should be linkeable ( either one way or both ways )
- A linked child base should allow the parent base to see the child's ideas. The indexs should be linked, and the child counts etc should be included in the parents.
- A child base should always be able to link to parent base ideas.

Jump to outbound references

Jump to inbound references

Navigation

Source file

reqlan rq/bases/base.rq

base.rq

file cluster

reqlan rq/bases

folder cluster

status: Not present

status cluster

tag: Not present

tag cluster

Printable page

Static print-friendly idea sheet.

Attributes

KeyValue
todo true

Browse all attributes

Ancestor context

No ancestor chain recorded.

Outbound references

KindIdeaPathSnippet
None

Inbound references

KindIdeaPathSnippet
None

Unresolved references

KindIdeaPathSnippet
None

Local graph

Initialising graph…