Project Plan

From SNEEP

Jump to: navigation, search

Contents

[edit] Overview of Project

[edit] 1. Background

A recent JISC report (Franklin and van Harmeln (2007): " Web 2.0 for Content for Learning and Teaching in Higher Education") recommended the undertaking of projects "investigating how institutional repositories can be made more accessible for learning and teaching through the use of Web 2.0 technologies”.

One key feature of the many applications generally classed as "Web 2.0" is the concept of collaboration and discussion focused on a particular digital object. In the case of a blog or wiki, that object is a post or page, which may typically be bookmarked and discussed in a collaborative manner.Essay writing help In the case of social or academic bookmarking (Delicious, CiteULike) the object is a bookmark or a bibliographic record, which may be tagged, discussed or otherwise shared. Other prominent Web 2.0 applications, such as YouTube or Flickr, have videos or photographs as their focus. Comments, tags, bookmarks, etc, can thus be seen as a distinct layer of data, associated with an object, on the one hand, and a user on the other.

Eprints repositories already possess the capability to manage both digital objects and registered users. Eprints version 3 has also introduced a plugin architecture, enabling third top weight loss pills party functionality to be added to repositories as extensions, without modification of the underlying distribution code.

This project will therefore develop a small suite of plugins, providing Eprints approved loan modification repositories with extensions that add key Web 2.0 features in a noninvasive way (i.e. without modifying the core metadata for the digital objects in the repository, or the core distribution code of the application).essay writing User contributed content will be managed apart from the main records, but displayed in the main item metadata view (comments, tags), or in the user's account management view (bookmarks) as appropriate. It is anticipated that many users may already use online social and collaboration tools (e.g. Del.icio.us, CiteULike) which can be used effectively with Institutional Repositories in a noninvasive way. Many others, however, will not, so it seems desirable that, among the community of users of a repository, a basic level of functionality, focused on the Diets that Work Fast for Women repository's content, should be provided. Web 2.0 savvy users may continue to use their preferred external tools, or use these Eprints Extensions. Bookmarks and tags collected using the Eprints Extensions will have several userconfigurable options for sharing and viewing (e.g. tag clouds), and will be exportable in the most widely used Wow leveling guide adipex formats (identified by preliminary research).

[edit] 2. Aims and Objectives

essay writing This project will extend the functionality of Eprints Institutional Repository software to include key Web 2.0 collaborative/sharing features, based on bookmarking, tagging and commenting. It will develop chiropractor san francisco fully working models of web software link building service to incorporate these functions into Eprints. The output will be made openly available for reuse and further development by the community help me write my essay.

[edit] 3. Overall Approach

[edit] 4. Project Outputs

  • A fully functional set of Web 2.0 plugins for Eprints.
  • Documentation for installation san francisco personal injury lawyer and use of plugins.
  • An evaluation of the use and effectiveness of the tools in a live IR environment.

[edit] 5. Project Outcomes

  • An understanding of current use and expectations of Web 2.0 class features among IR managers

and users

  • An online community portal focused on discussion of using Web 2.0 and IRs

[edit] 6. Stakeholder Analysis

Stakeholder Interest Importance
Eprints users (repository admins etc) Enhanced repository functionality High
Eprints team at Soton Confirm collaborative/open nature of Eprints High

[edit] 7. Risk Analysis

Risk Probability (1-3) Severity (1-3) Score (out of 9) Action to prevent/manage risk
Staff unavailabilty owing to conflicting priorities Medium High 6/9 Liaison with ULCC management and JISC PM
Lack of community engagement with project/outputs Low Medium 2/9 Community has already expressed considerable interest and engagement; further dissemination and publicity will support and expand user base.
Plugins do not work Low High 3/9 Basic concept already proven. Test and quality plan will ensure outputs fit for purpose.
Plugins do not work with imminent next version of Eprints (3.1) Medium High 6/9 Close liaison with Eprints team to ensure continued compatibility. (See Exit and Sustainability Plans.)
Scope creep Medium High 6/9 Ensure specs are agreed, and limit scope to functions specified.

[edit] 8. Standards

Platform: Linux and web Software: Eprints 3 (Perl, XML, MySQL, Apache) Metadata standards: RSS, Atom

[edit] 9. Technical Development

  • Specs will list required functionality for each plugin, supported by use cases/scenarios as appropriate.
  • Test cases will be ennumerated and based on specifications and managed on the wiki
  • Test results will be published/maintained on the wiki. Testing will take place after alpha and beta releases.
  • Code changes will be managed in CVS repository
  • Documentation will be drafter on the wiki, and maintained in repository with code base

[edit] 10. Intellectual Property Rights

SNEEP plugins will be published on the same basis as Eprints software (GNU).

[edit] Project Resources

[edit] 11. Project Partners

ULCC

[edit] 12. Project Management

Richard Davis

[edit] 13. Programme Support

Andy McGregor; JISC RRT

[edit] 14. Budget

Directly Incurred Staff October 07 - March 08 (Projected) October 07 - March 08 (Actual) Total
PM (including planning, publicity, dissemination, JISC liaison) (10d) £2401.50 £2401.50
Analysis, design, specification (8d) £1921.24 £1921.24
Development (25d) £6003.85 £6003.85
Testing (5d) £1200.78 £1200.78
Release, change, package management (4d) £960.63 £960.63
Total Directly Incurred Staff (52d) £12,488.00 £12,488.00
NonStaff October 07 - March 08 (Projected) October 07 - March 08 (Actual) Total
Travel and expenses 0 (bristol meeting Nov 07) 0
Hardware/software 0 0
Dissemination 0 (eprints pow-wow Dec 07) 0
Evaluation 0 0
Total Directly Incurred NonStaff 0 0
Total Directly Incurred 0 0
Directly Allocated October 07 - March 08 (Projected) October 07 - March 08 (Actual) Total
Staff
Estates £2,111.00 £2,111.00
Other
Directly Allocated Total
Indirect Costs £10,290.00 £10,290.00
Total Project Cost £24,889.00 £24,889.00
Amount requested from JISC £20,000.00 £20,000.00
Institutional Contributions £4,889.00 £4,889.00
Percentage Contributions over the life of the project ULCC: 20%, JISC: 80% Total 100%

[edit] Detailed Project Planning

[edit] 15. Workpackages

See Workpackages

[edit] 16. Evaluation Plan

Timing Factor to Evaluate Questions to Address Method(s) Measure of Success
End of project Functionality of plugins Do plugins meet mimnimum specifications Internal and 3rd party testing
End of project Ease of installation Are plugins easy to install (in relation to level of difficulty of Eprints installation) Internal and 3rd party testing
End of project Integration with external systems (RSS readers etc) Can newsfeed outputs from plugins be easily fed to and read by external systems Internal and 3rd party testing
End of project Usefulness of plugins/functionality Is the functionality likely to be of immediate use in the community? Consultation with community
End of project Future enhancements How could the work be taken forward? Consultation with community

Several Eprints installations have expressed an interest in using these plugins (Lincoln, for example, is interested in bookmarks and comments) and we will seek their assistance in testing the plugins outsider our own environments.

[edit] 17. Quality Plan

  • Work to agreed Specification, Test Plan and standards
  • Ensure Test Plan is completed by internal third-party
  • Produce public alpha and beta releases for third-party testing and feedback

[edit] 18. Dissemination Plan

[edit] 19. Exit and Sustainability Plans

  • Publish code and documentation in open code repository, preferably same location as core Eprints distribution.
  • Ensure that plugins compatibility with imminent 3.1 release of Eprints through close liaision with Southampton and Ep-tech list
  • Continue use of plugins in ULCC hosted repositories, and continue to feedback enhancements to the community, through Ep-tech list

[edit] Appendixes

[edit] 1. Workpackages

See Workpackages

[edit] Related Links:

palm beach condos FIA Card Services Worldpoint FIA Card Services Rewards FIA Easy Pay


cracked heels treatment professional essay writers banner syok Top banner Focus onSport News Cheap Travel Cheap Hotel VIP travel tips holiday to climb and take photo travel media to egypt main leadeship conference Dissertation Help Logo Design Contest buy an essay online Cheap Custom Essays Write My Essay buy essay online financial force perfect financial works call free financial advisory compare insurance company be a financial leader raise your fund best way to get rich Finance and Insurance Companies' show Sea Product Export buy research paper analysis essay UK Essay Writing buy research paper dayly travel in air flight Clarington Bed and breakfast local surfer Pacific travel Passion to tour and travel Travel News TP Tours and Travel Essays Help write my essay catalog design cheap custom essays essay help uk Buy Lanoxin Online

Retrieved from "http://sneep.ulcc.ac.uk/wiki/index.php/Project_Plan"
Personal tools