| 1. Integrate |
Access to Institutional Repository content |
Automatic collection of metadata when repository items included in packs, supported for EPrints and Fedora. Trials with friends and family then release on myexperiment.org. Extension to version-checking for packs. Interconnection of people identifiers between myExperiment & repositories. |
2 months + 1 month trials |
| 2. Discovery |
Developing enhanced discovery capabilities |
Autogeneration of tags, support for user-provided controlled vocabularies. Ranking, faceted browsing. Indexing of packs. Support for tagging and advanced search through other interfaces eg iGoogle, Facebook. Related search and recommendation. |
4 months |
| 3. Curation |
Enhanced curation support |
Support of expert curation, e.g. annotation of content quality. Improving community curation, including use of external references into content. Automation to assist the curation process. Trials with expert curators using workflow content. |
3 months |
| 4. Stores |
Access to native content |
Integration with web sites which support specific content types e.g. flickr, slideshare, sourceforge. Access to blogs. Investigation of Fedora as scalable store for myExperiment. Use of cloud storage services, e.g. DropBox. Use of desktop sync tools. Preservation strategies and planning. |
3 months |
| 5. Interop |
Linked data and linked people standards compliance |
Use of shared naming scheme (Science Commons). Interworking with Opensocial and Google Friend Connect. Support for SIOC. Federation of myExperiment servers. Compliance with linked data guidelines. Expression of relationships between repository artefacts using e.g. SWAN ontology. Use of coreference resolution services. Linking with Biocatalogue. |
4 months |
| 6. Enhancement |
Enhanced Institutional Repository use |
Use of myExperiment to discover repository content. Repository users provided with myExperiment functionality to improve discovery. Automation of deposit into repository from myExperiment, including ORE. Trials with specific groups. |
3 months |
| 7. Evolution |
Evolved software base |
Provision of myExperiment functions through new components and services that can easily be reused in other environments, and incorporation of functions from other projects which are using myExperiment. |
4 months |
| 8. Trials |
Trials and evaluation |
Studies of specific user groups, coupled with analysis of broader uptake of enhanced functionalities in myExperiment users and repository users. User groups include Life Science, Chemistry, and encompass learning & research. |
4 months across year 2 |
| 9. Community |
Community engagement & dissemination |
Continuous programme of user workshops, dissemination and consultation through workshops and conferences, including digital citation, open repositories, e-research communities, JISC conferences, IE and VRE events. |
3 months (2.5 days / month) |
| 10. Servers |
Server support and maintenance |
Maintaining the operational service on the myexperiment.org server, the virtualised alpha test server for production and sandbox server for API users, including backups, system maintenance, security patches, performance monitoring, collection and analysis of usage data, NAGIOS monitoring and hardware upgrades. |
3 months (2-3hrs / week + 1 day / month) |
| 11. Evaluation |
Evaluation against objectives |
Continuous cycle of evaluation against our three project objectives and the running of the project against the project plan. Evaluation of the repository itself as fit for purpose for all stakeholders |
2 month |
|
