All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
The familiar parent/child metaphor can be used to explain how it works. Every community in DSpace can be either a 'parent' community‚ meaning it has at least one sub-community, or a 'child' community‚ meaning it is a sub-community of another community, or both or neither. In these terms, an 'orphan' is a community that lacks a parent (although it can be a parent); 'orphans' are referred to as 'top-level' communities in the DSpace user-interface, since there is no parent community 'above' them. The first operation‚ establishing a parent/child relationship - can take place between any community and an orphan. The second operation - removing a parent/child relationship‚ will make the child an orphan.
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e0052909-9e6a-43de-9d8e-3d5b383d7668"><ac:plain-text-body><![CDATA[ | Command used: |
|
Java class: | org.dspace.administer.CommunityFiliator | |
Arguments short and (long) forms: | Description | |
| Set a parent/child relationship | |
| Remove a parent/child relationship | |
| Child community (Handle or database ID) | |
| Parent community (Handle or database ID | |
| Online help. |
...