...

To see what's in store for the future, see Next Release Status and the DSpace RoadMap.

Where can I download the DSpace open

...

source software?

DSpace is freely available as open - source software from SourceForge.

...

To view the DSpace log live

 ## In Linux, run the following command then reproduce the internal error state
 ## use the pathname prefix appropriate to your DSpace installation
 tail -F /var/logs/dspace.log

 ## and you should see something of the kind

2009-05-18 12:52:45,935 WARN  org.dspace.app.webui.servlet.DSpaceServlet @ name\
@place:session_id=F32DD4066DD475B8841A2A2204961B9A:ip_addr=1.2\
.3.4:database_error:org.postgresql.util.PSQLException: ERROR: duplicate key \
violates unique constraint "metadatafieldregistry_pkey"
org.postgresql.util.PSQLException: ERROR: duplicate key violates unique constra\
int "metadatafieldregistry_pkey"
        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryE\
xecutorImpl.java:1525)

What's the best strategy for backing up/restoring DSpace?

...

See LocaliseCreativeCommons

DSPACE with ISO-8859-1 and others

...

encodings

If you want to use an encoding other than UTF-8 you can edit the file src/org/dspace/storage/rdbms/DatabaseManager.java and modify the next lines

  else if ((jdbctype == Types.CLOB && "oracle".equals(dbName)) || jdbctype == Types.VARCHAR)
  {
    // Support CLOBs in place of TEXT columns in Oracle
    row.setColumn(name, results.getString(i));
  }
  /*else if (jdbctype == Types.VARCHAR)
  {
    try
    {
       byte[] bytes = results.getBytes(i);
       if (bytes != null)
       {
           String mystring = new String(results.getBytes(i), "UTF-8");
           row.setColumn(name, mystring);
        }
        else
        {
            row.setColumn(name, results.getString(i));
        }
     }
     catch (UnsupportedEncodingException e)
     {
         // do nothing, UTF-8 is built in!
     }
   }*/

Clearing Cocoon (XMLUI) cache

Apache Cocoon, the DSpace component XMLUI is based on, keeps a cache of visited pages to speed up access to them. This can pose a problem usually during development of XMLUI themes, when you update XSL, but an older version of the page is served from cache instead of the current version being constructed. It's safe to clear the cache, the only impact it can have is on speed until the cache is repopulated.

In DSpace 1.8.0 and newer, there is a convenient link in XMLUI to clear the cache without restarting the servlet container:

1. log in as DSpace administrator
2. click on "Control Panel" in the sidebar menu
3. click on the "Java Information" tab
4. click on the "(Clear Cache Immediately)" link

Next to that link, you can also see how many pages are currently cached.

In DSpace versions up to 1.7.2, you have to clear the cache manually by shutting down Tomcat, deleting the cache directory and then restarting Tomcat:

1. Code Block
   ${tomcat6.home}/bin/shutdown.sh

2. Code Block
   cd ${tomcat6.home}/work/Catalina/{appropriate.domain.dir}/_/

3. Code Block
   rm -rf cache-dir

Depending on your Tomcat version, whether you used a package and where you installed it, some common locations of the cache directory are:

/var/cache/tomcat5/work/Catalina/localhost/xmlui/cache-dir
/var/lib/tomcat6/work/Catalina/localhost/_/cache-dir
/opt/tomcat6/work/Catalina/localhost/xmlui/cache-dir
/usr/local/tomcat6/work/Catalina/localhost/xmlui/cache-dir