User Services and Applications Working Group

Overview and Update

Rhonda MarkerCommittee on Scholarly Communication

September 18, 2008

US&AWG organization

Cabinet

AUL/DLS (Grace Agnew)

Cyberinfrastructure Steering Committee

Metadata Working

Group (Mary Beth Weber,

Chair)

User Services & Applications Working

Group (Rhonda Marker & Linda Langschied, co-

chairs)

Ad Hoc Working Groups

Software Architecture Working

Group (Ron Jantz, chair)

Library Resources

Council

memberCommittee on Scholarly

Communication

member

User Services WG members

• Rhonda Marker, co-chair rmarker@rci

• Linda Langschied, co-chair langschi@rci

• Rebecca Gardner rgardner@rci

• Karen Hartman khartman@rci

• Triveni Kuchi kuchi@rci

• Jim Niessen niessen@rci

• Kalaivani Ananthan ananthan@rci

User Services WG: Charge

• Identify and prioritize applications needed to support preservation, access and services to RU faculty

• Investigate existing services and applications offered by other Fedora sites for potential reuse by the RU repository

• Develop an application testing plan, involving both alpha and beta testing, for usability and functionality

RUcore Development Steps (1)

• Software Architecture (meets twice monthly):– Structures release calendar: Release numbers,

sequences, and estimated dates– Assigns upgrades, new functions, and changes to a

specific Release number– Evaluates dependencies, feasibility, staffing needs

for tasks– Sets deadlines for requirements/specifications– Schedules testing and release dates

RUcore Development Steps (2)

• User Services & Apps WG (meets monthly)– Develops requirements– Writes specifications– Sends specifications for review

• Software Architecture WG• Metadata WG• Cyberinfrastructure Steering Committee

– Writes ancillary specifications:• Software Architecture WG• Metdata WG

RUcore Development Steps (3)

• RUcore Developers:– Receive specifications and “bug reports”– Writes and edits system code– Code installed in system for testing

• Repository Application Manager/WMS Manager:– Advises Software Architecture WG on testing dates– Trains testers– Schedules and conducts testing sessions

RUcore Development Steps (4)• Testing and Implementation Sequence:

– New code placed on test/development server in SCC (“lefty”)

– Testing on lefty, 3-6 weeks– Revised code moved to staging server in TSB (“mss2”)– Test on mss2, usually 1 week– Tested code moved to production server in TSB

(“mss3”)– Sanity Test on mss3, one day

• Production server down during code installation & testing– New release to public

User Services WG Scope (1)

• RUcore (Rutgers Community Repository)– Web pages– Search interface– Next release:

• Order search results by Name (in addition to Title, Date)

• Limit searches by language, peer-reviewed• Display Name in brief record (search hit display)• Highly configurable Partner Portal for departmental

and personal web pages

User Services WG Scope (2)

• New Jersey Digital Highway– Web pages and search interface– Next release: improved browse searches

• New Jersey counties• Historical periods

User Services WG Scope (3)• Faculty Deposit

– Web pages, search interface, deposit forms, statistics and reports

– Major features in next release:• Third party (agent) deposit• Grant-funded research deposit• Co-author collection assignment• Standard citation note• Embargo option• Faculty Survey interface• Peer-review article identification• Faculty collection statistics

User Services WG Scope (4)

• RUetd search interface• Future release: better integration with other

RUcore functions

User Services WG Scope (5)

• RUcore/NIH Public Access– Web pages and deposit forms– Next release: forms incorporated into Faculty

Deposit (no separate deposit)

“Typical” Development Timeline• Specifications deadline: August 31

– Specifications co-reviewed by Working Groups: July-Augustmany steps occur here

• Coding completed: October 15• Install new code on lefty: October 15-19 [… some delays …]• Testing on lefty: October 25-November 30• Install code on mss2: December 4-5• Testing on mss2: December 6-19 [… some delays …]• Notification of downtime to public: December 20, reminder on January 3• Install code on mss3: January 8 (evening)-January 9• Sanity test on mss3: January 9 (afternoon)• Full implementation on production server: January 9, 5:00 pm