Page History
...
The primary delivery framework for the KnowledgeBase is the text-based guide. The DuraSpace KnowledgeBase includes three separate Confluence wiki "spaces":
1) the umbrella DuraSpace KnowledgeBased, used for general content and information (such as this guide)
2) DSpace KnowledgeBase
3) Fedora KnowledgeBase
Each KnowledgeBase has a left-hand navigation menu which provides an easy way to find your way around to various topics and sub-topics as well as the ability to jump between the DSpace KnowledgeBase and the umbrella DuraSpace KnowledgeBase. A fully expanded view of the navigation menu or site map can be viewed here: DSpace Site Map, Fedora Site Map
wiki guide. Before you start creating any content, please review the information about the KnowledgeBase structure and navigation here.
This page is a sample template of the text-based guide orientation of each way to jump between each of the KnowledgeBase "spaces" as well as an orientationThis page is a sample template that should be used when creating any new text -based content.
You can explore the current Table of Contents using the left-hand navigation menu
. Within the guide there is the option of including helpful images (screenshots, diagrams, etc.), links to screencast/webinar recordings, presentation slides, as well as links to other helpful resources.
We welcome all contributions and ask that you make use of this template to format your text-based content. If you have any questions or feedback, please contact Valorie Hollister at vhollister@duraspace.org.
small sample of the curriculm is fleshed out – different bullted topics, more obvious stmt about where they can contribute: we created the outline and subpages – welcome to comment on that, welcome to make contributions corresponding to the existings TOC or suggest and create a new one.
-full outline somewhere – planned for the future or where I can sugest things planned for the futureàmacro?
-put site map page for each fedora and dspace
content by copying and pasting this page from/to the Wiki Markup editor.
As you write content focus on keeping language accessible so that anyone can understand itType your content paragraphs here. Focus on keeping language accessible for anyone to understand, regardless of their technical background. Avoid using acronyms and jargon. When ever possible insert examples or images (screenshots, diagrams, etc.) that may help visualize your point/s. If you know of helpful references (conference presentations, papers, etc) create links either within the main content text or at the end in the "Hungry for more?" section. If you have questions on how to create a screencast so you can demonstrate how to do a specific task, click here.
Formatting tipsLinking Instructions:
To insert an image, use the following code:
...