Skip to end of metadata
Go to start of metadata

The wiki you are viewing is based on Confluence.

We have turned on anonymous read-only access for the Infrastructure space in Confluence. The permissions are currently quite permissive, with only a few "sensitive" pages having restricted access. Our goal is to allow other digital library developers to see what we're doing, with the understanding that information on the wiki is primarily intented for our internal use. The information may be outdated, in-progress, and often quite blunt. Nothing here has been cleaned up for "presentation" to the public.


Exports can take a long time. The export is automatically packaged into one large zip file, and deliverd to your web browser (this means you don't choose a destination directory until the export is actually complete). The page hierarchy will not be preserved.

When exporting, you can choose which pages will be included in the export. Links to pages that are included in the export will be converted into relative links. Links to pages that aren't included in the export will continue to point to the live Confluence page.


The default table-handling system in Confluence is awful, and anything more than the simplest table requires HTML coding (which many administrators don't want to enable). One possible alternative is the Content Formatting Macros plugin.

Including JIRA content

To include a list of JIRA issues in a Confluence page:

  1. In JIRA, perform a search, browse, or anything else that creates an "Issue Navigator" result screen.
  2. Near the top, you will see a set of viewing options that includes Browser, Printable, XML, Full Content, etc. Copy the URL of the "XML" link to a temporary location.
  3. In Confluence, add a macro that looks like {jiraissues:url=JIRA-URL&os_username=johnsmith&os_password=secret},
  4. In the macro, replace JIRA-URL with the URL copied from JIRA.
  5. In the macro, replace johnsmith and secret with a valid JIRA username/password. It is best to not use your own username/password, because anyone who can edit the Confluence page will be able to see it. It is better to use the "guest" username/password.

Task lists

Confluence's fancy "task list" objects, like {dynamictasklist:thingsToDo}, are a quick and easy way to organize tasks, but be careful with them. Anyone who can view the page may edit the lists. This includes anonymous users, if the page allows them.

  • No labels