DSpace+1.6.0 RC2 Testathon - The Big Bug Hunt!

align="right"

Welcome

Welcome to the DSpace Testathon page for version 1.6.0 Release Candidate 2 (RC2).

The 1.6.0 RC2 Testathon takes place during the week of February 15 through 19, 2010.

Please get involved with the DSpace+1.6 testathon! We rely on testing by the whole community to ensure that we weed out as many bugs as we can before we release the software. Not only will this help us make DSpace 1.6 the best it can be, but it will allow you to try out some of the new features of DSpace 1.6.

Keep an eye out for these new features in DSpace+1.6:

• Enhanced statistics
• Embargo facility
• Batch metadata editing
• Improved documentation
• Authority control lists
• Community administration

Stuart Lewis, 1.6.0 Release Coordinator, has a blog post entitled DSpace+1.6 - What will be in it for me? which provides more detail around the new features available in DSpace 1.6.0.

Getting Started

• Visit one of the test instances listed below to begin testing immediately.

• Unsure of where to start? We have a list of common tests that may be performed in the below Testing Scripts section.

• If you are technical, you can also install a local copy of 1.6.0 Release Candidate 2 (RC2) to test on your own server environment. See the below section on Downloading DSpace+1.6.0-RC2.

• You can also help us review our new DSpace+1.6+Documentation. If you run into any issues with the documentation (errors, omissions, confusion), please report it similar to a bug/issue (see below section on Providing Feedback / Reporting Bugs) so that we can get it cleaned up before the final 1.6.0 release.

• If you run into any problems, please report them as detailed in the section on Providing Feedback / Reporting Bugs. That way we can be sure they get fixed before the final release!

Test instances

To start testing immediately, visit one of these public test instances.

Getting Administrative or Special Access Rights

• For the quickest way to get Administrative or Submitter access, visit our chat room (visit http://dspace.testathon.net/ , give yourself a nickname and click "Login"). Someone is usually able to give you access immediately. You will need to register your email with one of the below sites first.
• Otherwise, register with the site you want access to, and send an email to the contact listed below.

  • tspacetest.library.utoronto.ca

    sites
    • Contact Gabriela Mircea (tspace [AT] tspace.library.utoronto.ca) or Tim Donohue (tdonohue [AT] duraspace.org)

XMLUI test instances (all are updated to 1.6.0 RC2)

• http://tspacetest.library.utoronto.ca:14080/xmlui

JSPUI test instances (all are updated to 1.6.0 RC2)

• http://tspacetest.library.utoronto.ca:14080/jspui

OAI-PMH test instances (all are updated to 1.6.0 RC2)

• http://tspacetest.library.utoronto.ca:14080/oai

SWORD test instances (all are updated to 1.6.0 RC2)

• http://tspacetest.library.utoronto.ca:14080/sword/servicedocument

Download DSpace+1.6.0-RC2

SourceForge Zip Files

Zipped up versions of DSpace+1.6.0-RC2 are available on SourceForge at http://sourceforge.net/projects/dspace/files/ . Download one of the Zip files under the "DSpace Release Candidate / 1.6.0-rc2" folder. Two releases are available:

• dspace-1.6.0-rc2-release

  - This is the binary release (no source code included).

• dspace-1.6.0-rc2-src-release

  - This is the Source release including all DSpace source code.

Subversion

The full DSpace+1.6.0-RC2 source code can also be downloaded from Subversion:

Providing Feedback / Reporting Bugs

There are different ways of providing feedback:

• To report bugs, please feel free to use our bug tracking software JIRA: http://jira.dspace.org/
  • If you don't yet have an account, visit the JIRA Signup page to set one up.
• Alternatively, you can email bug reports to the dspace-devel@lists.sourceforge.net dspace-devel mailing list - Please begin your email subject with "1.6RC2 Bug" (or something similar). NOTE: You must sign up for the dspace-devel mailing list in order to post messages.
• For additional support or to talk about bugs or issues, please feel free to join us in the DSpace IRC channel (#dspace). The channel can be found at #dspace on chat.freenode.net. The easiest way to login is to visit our DSpace Testathon webpage (http://dspace.testathon.net/), fill out a nickname (of your choice) and click Login.
  • Alternative way to login to #dspace
    • Visit http://webchat.freenode.net/
    • Enter in a Nickname (of your choice)
    • In the "Channels" field enter "#dspace" (without the quotes)
    • Leave "Auth to Services" unselected
    • Click Login

Testing Scripts

The below scripts can be used as a starting point for any DSpace Testing you wish to perform. They may not be 100% complete, so feel free to test other features you come across.

If you feel comfortable editing this wiki page, you may also note any features you've successful tested below (be sure to add your name after any comments you make).

• If you don't yet have a Wiki account, you can visit the "Log in / create account" link at the very top of this webpage. After creating your account, visit this page and click on the "Edit" link next to the section you wish to edit.
• If you don't have the time to add your notes to this Wiki page, don't worry about it. Just please report any bugs or problems you have, so that we can get them fixed!

If you've found a bug, report it by following the instructions in the Providing Feedback / Reporting Bugs section above.

Updated Documentation for 1.6

There are substantial upgrades to the DSpace documentation for version 1.6. Volunteers are needed to review it for clarity and accuracy. Visit the 1.6 Documentation page for more info: http://wiki.dspace.org/index.php/DSpace+1.6+Documentation

Issues Fixed between 1.6.0RC1 and 1.6.0RC2

The following issues/bugs were located during the 1.6.0 RC1 Testathon, and are now marked as "fixed" in 1.6.0 RC2.

These bugs are worth re-testing to ensure they are fully resolved before 1.6.0 final.

• DS-398 - Submission license displayed on collection and item homepage
• DS-399 - Special characters in collection license lead to parse error
• DS-400 - Webui item browse (date, title or similar) reduces displayed issue date by one day
• DS-405 - New 1.6 Statistics settings in dspace.cfg need Documentation
• DS-406 - View Statistics button does not work in item page
• DS-407 - Install or Upgrade on existing server throws errors for "mvn package"
• DS-409 - JSPUI Statistics Display ignores "statistics.item.authorization.admin"
• DS-410 - Updates to Upgrade Instructions necessary
• DS-412 - Xpdf MediaFilter: generate UTF-8 text, and improve error reporting
• DS-414 - solr statistics file downloads listed in statistics display of communites and collections
• DS-415 - Create groups via admin UI authorization denied
• DS-417 - 1-day (or passed) embargo dates give error upon submission
• DS-418 - i18n broken in jspui
• DS-419 - Setting embargo.field.terms to an unqualified field throws uncaught exception on item submission
• DS-421 - Setting solr.metadata.item.X property to an unqualified field generates exception in SolrLogger.post on item view and prevents Solr from logging the event
• DS-422 - Directory 'etc' missing from Ant target 'init_installation'.
• DS-423 - Ant target 'clean_database' doesn't drop all tables'.
• DS-424 - Export metadata button displayed in JSPUI Administration List of withdrawn items
• DS-425 - JSP UI cosmetics: horizontal scroll bar
• DS-427 - Item license per default displayed in item display of the xmlui
• DS-428 - Wrong link for bitstreams during submission
• DS-430 - Embargo
• DS-432 - No mention of config/news-xmlui.xml in manual
• DS-436 - SWORD Authenticator doesn't support the special groups infrastructure
• DS-437 - Oracle DB Schema has artifacts from past releases
• DS-438 - JSPUI stats - filename incorrect on second and subsequent files
• DS-442 - Enable RSS feeds by default
• DS-444 - java.lang.ClassCastException: org.mozilla.javascript.NativeContinuation cannot be cast to org.mozilla.javascript.continuations.Continuation
• DS-445 - New Bitstream.findAll() method
• DS-446 - New ant step - test_database
• DS-447 - Email test script
• DS-455 - Remove dspace/config/log4j.xml
• DS-459 - OAI PMH is not delivering continuation tokens
• DS-460 - Change logging from RollingFileAppender to DailyFileAppender
• DS-461 - Add information about setting web proxies for maven to install docs
• DS-472 - 'fresh_install' broken on a completely clean system
• DS-477 - LDAPHierarchicalAuthentication fails when the LDAP returns mixed case email address

Web UI - JSP

• Accuracy and completeness of online help
  • standard help
  • administrator help

Admin UI - JSP (done)

• Communities and collections
  • Create new community
  • Create new sub-community
  • Create new collection
    • Create collection with template (Known Issue: http://jira.dspace.org/jira/browse/DS-397)
    • Create collection with own license
    • Create collection with one ore more workflow steps
    • Create collection with collection-admin
• Epersons and groups
  • Create new e-person (Known Issue http://jira.dspace.org/jira/browse/DS-403)
  • Create new group
  • Edit existing eperson
  • Edit existing group
  • Delete existing eperson
  • Delete existing group
  • Change groups which have been added to groups
• Items
  • Edit item
  • Withdraw and reinstate item as an admin
  • Withdraw and reinstate item as an collection admim
    • withdraw
    • reinstantiate - the collection administrator has no possibility to reinstantiate an item as he got no access to the admin withdrawn items or other possibility to get a list of his withdrawn items (2009-12-07 Claudia Juergen)
  • Move Items
  • Expunge item
• Registries
  • Metadata registry
    • edit schema
    • create new schema
    • edit field
    • create field
    • delete field
    • move field
  • Bitstream format registry
    • create new - note newly created bitstream formats not applied to existing bitstreams with this format(2009-12-07 Claudia Juergen)
    • edit existing
      • edit metadata
      • change internal flag
    • delete existing - wonder whether the license formats (default and CC) should be deletable at all (2009-12-07 Claudia Juergen)
• Admin tasks
  • Abort a workflow via admin UI -the admin should enter a reason and the submitter and workflow responsible should be notified (2009-12-07 Claudia Juergen)
  • Authorisation (see Authorisation below)
  • Edit top news on front page (test UTF-8 characters)
  • Edit side news on front page (test UTF-8 characters)
  • Edit License
  • Supervisors - wonder who really uses this feature, it has such a small scope, maybe we should ask via the lists. Some other admin tool to view in general unfinished submissions and lingering workflow tasks might be more useful (2009-12-07 Claudia Juergen)
  • Statistics (see statistics below)
  • Delete collection
    • on deleting the collection there should be more information about it's content for the admin. Maybe an automated export of the collection for the admin would be usefull too
      • items in the collection
      • items in submission
      • items in workflow
    • anything in progress should be deleted with notifications
      • ongoing submission
      • workflow task
  • Delete community - (2009-12-07 Claudia Juergen) see comments above on collection deletion same for community deletion
  • Metadata import (see Batch import below)

Miscellaneous UI - JSP

• Item Display
• Community and Collection Home Pages
  • Elements of the Home Page
  • Recent Submissions
• Configure metadata fields to appear in simple item display
  • Default
  • collection specific
• show strength of communities and collections
  • cached
  • not cached
• HTML documents (see also: Submission UI)
• RSS Feeds (not completely testable without a real handle server running)
  • For the top level
  • For a community
  • For a collection
• OpenSearch
• My DSpace
  • View and manage subscriptions (see also E-mail below)
  • View accepted submissions
  • View uthorization groups I am member of
  • Unifinished Submissions
    • Delete
    • View
    • Resume
  • Usability - could do with a bit of tidying up, not very concise (2009-12-08 Claudia Juergen)
  • Password forgotten
    • standard registered user
  • Register
  • Edit profile
    • User data
    • Change password
  • OpenURL links - we need a neutral Logo not the MIT Links one (2009-12-08 Claudia Juergen)
• Suggest an item
  • without login restriction
  • without login restriction
• Map an item from one collection to another
  • mapping - the mapping itself works, but the search for items to map is case sensitive in the jspui (Known bug http://jira.dspace.org/jira/browse/DS-402) (2009-12-07 Claudia Juergen)
    • collection, item was mapped to, browse indices
    • parent communities of this collection, browse indices
  • unmapping
    • collection, browse indices
    • parent communities, browse indices

Submission UI - JSP

*Creative commons licences

• • Switch on and off
  • Try using HTTP proxy via `http.proxy.host/port`
    *File
  • Submission with single file
  • Submission with multiple files
  • Upload HTML document (multiple files with primary bitstream)
    *Configure input-forms.xml
  • added/removed dc fields
  • added other metadata schema fields
  • using fields of different schemas
    *Recognised and unrecognised formats
    *Checksum verification
  • See below
    *Licences
  • Site default (check for UTF-8 characters)
  • Collection specific (check for UTF-8 characters)
• use of controlled vocabulary

Submission workflow - JSP

• Collections with no workflow steps, or a combination
• For each workflow step, test editing metadata
• Test accept and reject or new submissions

Authentication - JSP

under UI for now, since it's the only place it's currently used

• Simple login username/password
• Edit user profile
• Registration, forgot password
• LDAP server
  • Hierarchical LDAP
• Shibboleth
• X509 certificate
• Logging out

Search and Browse - JSP (nearly done)

• Configure columns in item lists (search results etc) using webui.itemlist.columns in dspace.cfg
• Browse communities and collections (1.6.0 RC2 has fix for bug http://jira.dspace.org/jira/browse/DS-400)
• Browse titles, authors, subjects, by date
  • With scope 'All of DSpace'
  • in a community
  • in a sub-community
  • in a collection
    Configure date, author, title, subject by using `webui.browse.index.` properties in `dspace.cfg`
  • add a new browse index
  • change order and properties
• Search
  • simple search
  • advanced search
  • change default search operator
  • configure search indices
  • Controlled vocabulary subject search
  • Try configuring a different analyzer (e.g. for Chinese)

i18n

• UI - (1.6.0 RC2 has a fix for bug http://jira.dspace.org/jira/browse/DS-418)
• emails

Web UI - XML

• Accuracy and completeness of online help - there is no online help for the xmlui atm (2009-12-08 Claudia Juergen)

Admin UI - XML

*Commuinities and collections

• • Create new community
  • Create new sub-community
  • Create new collection (1.6.0 RC2 has fix for bug http://jira.dspace.org/jira/browse/DS-398)
    • Create collection with template - (Known bug http://jira.dspace.org/jira/browse/DS-397)
    • Create collection with own license - (1.6.0 RC2 has fix for bug http://jira.dspace.org/jira/browse/DS-398 and http://jira.dspace.org/jira/browse/DS-399)
    • Create collection with one ore more workflow steps
    • Create collection with collection-admin
• Epersons and groups
  • Create new e-person
  • Create new group (1.6.0 RC2 has fix for bug http://jira.dspace.org/jira/browse/DS-415)
  • Edit existing eperson
  • Edit existing group
  • Delete existing eperson
  • Delete existing group
  • Change groups which have been added to groups
    *Items
  • Edit item
  • Withdraw and reinstate item as an admin
  • Withdraw and reinstate item as an collection admim
  • Expunge item - ok, but should the collection administrator be able to expunge items? At the moment he is (2009-12-09 Claudia Juergen)
    *Registries
  • Edit metadata registry - new DC fields
  • Move metadata fields between schemas
  • Edit metadata registry - new schema
  • Edit bitstream format registry
• Admin tasks
  • Abort a workflow via admin UI
  • Authorisation (see Authorisation below)
  • Edit top news on front page (test UTF-8 characters)
  • Edit side news on front page (test UTF-8 characters)
  • Edit License
  • Supervisors
  • Statistics (see statistics below)
  • Delete collection
  • Delete community

Miscellaneous UI - XML

• • Item Display *
  • default display
  • full display
  • Community and Collection Home Pages *
  • Elements of the Home Page - (1.6.0 RC2 has fix for bug http://jira.dspace.org/jira/browse/DS-398)
  • Recent Submissions
  • ** Recent Submissions list is different in xmlui from jspui
    *Configure metadata fields to appear in simple item display
  • Default (`webui.itemdisplay.default = ...`
  • Per-collection (`webui.itemdisplay.style = ...` and `webui.itemdisplay.style.collections = ...`
• show strength of communities and collections
• HTML documents (see also: Submission UI)
• RSS Feeds
  • FOr the top level
  • For a community
  • For a collection
• Translations
• My DSpace
  • View and manage subscriptions (see also E-mail below)
  • View accepted submissions
  • View uthorization groups I am member of
  • Unifinished Submissions
    • Delete
    • View
    • Resume
  • Usability
  • Password forgotten
    • standard registered user
    • not registered user, inactive user account
  • Register
  • Edit profile
    • User data
    • Change password
  • OpenURL links
• Suggest an item
• Map an item from one collection to another
  • mapping
    • collection, item was mapped to, browse indices
    • parent communities of this collection, browse indices
  • unmapping
    • collection, browse indices
    • parent communities, browse indices

Submission UI - XML

*Creative commons licences

• • Switch on and off
  • Try using HTTP proxy via `http.proxy.host/port`
    *File
  • Submission with single file
  • Submission with multiple files
  • Upload HTML document (multiple files with primary bitstream)
    *Configure input-forms.xml
  • added/removed dc fields
  • added other metadata schema fields
  • using fields of different schemas
    *Recognised and unrecognised formats
    *Checksum verification
  • See below
    *Licences
  • Site default (check for UTF-8 characters)
  • Collection specific (check for UTF-8 characters)

Submission workflow - XML

• Collections with no workflow steps, or a combination
• For each workflow step, test editing metadata
• Test accept and reject or new submissions
• Controlled vocabulary

Authentication - XML

under UI for now, since it's the only place it's currently used

• Simple login username/password
• Edit user profile
• Registration, forgot password
• LDAP server
  • Hierarchical LDAP
• Shibboleth
• X509 certificate
• Logging out

Search and Browse - XML

• Configure columns in item lists (search results etc) using `webui.itemlist.columns` in `dspace.cfg`
• Browse communities and collections
• Browse titles, authors, subjects, by date
  • With scope 'All of DSpace'
  • in a community
  • in a sub-community
  • in a collection
    Configure date, author, title, subject by using `webui.browse.index.` properties in `dspace.cfg`
• Try configuring a different analyzer (e.g. for Chinese)
• Basic and advanced search
  Configure search fields (`search.index.` in `dspace.cfg`)
• Controlled vocab subject search

Advanced functionality

OAI-PMH

*Validate:

• • Validate using http://www.openarchives.org/data/registerasprovider.html - see http://www.openarchives.org/Register/ValidateSite?log=3442 for details (2009-12-08 Claudia Juergen)
  • Validate using Repository Explorer
  • Extract METS, DIDL; ensure valid XML
• Ensure correct exposure of items when restriction setting in dspace.cfg is enabled

Batch import/export

• Test import
• Test export

ItemUpdate

• Add metadata
• Delete metadata
• Add bitstream
• Delete bitstream

Media Filters

• Thumbnail generation
• Full-text extraction and indexing
• Configure to support different bitstream formats
• Test collection flag

E-mail

• Configure an SMTP server that needs authentication, try sending mail (e.g. 'forgot password' mail)
• Send feedback using link in footer
• Get error alerts
• Test subscriptions (`subs-daily`)
• Test forgot-password email
• Test 'new user registration' email facility
• Email to user after successful submission
• Email from checksum checker

IP Based Authentication

• single
• truncated
• range

Statistical reports

• Check they work and are counting correctly

Checksum checker

• Change a file and check the reporter catches it
• Change file back to original and check the report is clear
• Sends emails correctly (see 'E-mail' section above)
• Check across multiple asset stores

SWORD

• Request a service document, ensure it matches the collection deposit authorizations for that user
• Deposit an item
  • (See: http://testathon.net/EasyDeposit/ for help)

OAI-ORE Harvesting

• Test Creating a Collection which Harvests metadata-only items via OAI-PMH
• Test Creating a Collection which Harvests files + metadata via OAI-ORE enabled site (e.g. another DSpace with OAI-ORE enabled).

Installation, Updating, Deployment

• Test fresh install
  • on IBM AIX
  • on Windows
  • on Linux

• Test update from 1.5.x with existing data + configuration
• Update customised/modified DSpace, find 'gotchas'
• See also Handle Server
• Test on:
  • Linux
  • Windows
  • Mac
  • other UNIX

Under the bonnet/hood

• Validate Plugin Manager configuration by running command: `bin/dsrun org.dspace.core.PluginManager` and then check log for errors and warnings.

Database platforms

*Test fresh install

• • On Oracle 9.2 on Windows 2003 Server
  • On Oracle 10.1 on Windows 2003 Server

*Test 1.5.x->1.6 upgrade

• • On PostgreSQL
  • On Oracle (version numbers?)

Bitstream storage

• Multiple asset stores
  • Add second asset satore and ensure new submissions go in there.
  • SRB

Handle Server

• Install/update and test a 'live' Handle Server (connect to global)

Authorisation

• Default permissions (on submission)
• Remove read access, check access not possible (on bitstreams)
• Check unauthorised users cannot access admin UI, edit community/collection/item screens, submit
• Community administrator role
• Community admins can create new sub-communities and collections.
• Collection administrator role
• Collection admins can withdraw/reinstate items with the default "COLLECTION_ADMIN" privileges.

Content API

TODO - What needs to be tested here?

Packagers, crosswalks

• Need feedback on API
  • Test with `org.dspace.app.packager.Packager` command-line app.
  • Configure dissemination crosswalk plugins as OAI formats, see `config/templates/oaicat.properties`

Batch jobs

*Test batch jobs:

• • dspace (script launcher)
  • cleanup
  • create-administrator
  • dspace-info.pl
  • dspace_migrate
  • indexer (index-init and index-update )
  • make-handle-config
  • metadata-export
  • metadata-import
  • packager
  • stats
  • structure-builder
  • sub-daily
  • update-handle-prefix

Bugs and other issues found

You may list any bugs found here. Please also submit an official bug report as detailed in the Providing Feedback / Reporting Bugs section above.

Known Issues still outstanding, and not resolved by 1.6.0 RC2 (Check specific items for status, comments or scheduling)

• DS-429 Item withdrawal/tombstoning
• DS-426 Item's submission license accessible without beiing configured to be public (jspui)
• DS-420 Community admin unable to delete items mapped to other collections.
• DS-413 solr statistics evaluation timespan should be displayed
• DS-411 XMLUI itemSummaryList-DIM only matches first possible author metadata
• DS-404 Notifications for submitter and workflow task responsible on workflow abortion through administrator
• DS-403 Registration Notification with null data for eperson created by the administrator
• DS-402 Item mapper search case sensitive (jspui only)
• DS-401 Wrong date issued during submission
• DS-397 Collection template metadata language qualifiers ignored

New issues found in 1.6.0 RC2

• Add any newly found issues here