You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Problem definition

Description of the problem to be solved by this working group

Scope

Description of the scope of the working group

Role

Description of the role that the working group plays

Results and deliverables

Date

Result/Deliverable

Description

Status

 

 

 

 

 

 

 

 

Members

User list not rendered as you do not have the privilege to view user profiles.


Related pages

 
Proposal for the creation of KE Usage Statistics Guidelines
- what would be the measurable goal of the activity
An agreed set of "KE Usage Statistics guidelines ".Emphasize these are guidelines NOT standards! (Profile for using appropriate standards)(what does agree mean: representative of each project in each country has agreed, by putting the name of the projects on the guidlines under the section "Endorsement" )- what the results/benefits would be
Freely available guidelinesStandardisation ofUsage Statistics Exchange, across current and futurre projects. This leads to Confidence , transparency, trust, reliability and interoperability.- who would be using the results - for what purpose
, * = directly involved in this proposal.
Three MAIN groups:*Developers: for implementing the guidelinesRepository administrators: providing usage dataAnalysts: work with the usage data 
Other Stakeholders, including:End Users: guide to popularity,Funders: they could demand adoption of these guidelinesPublishersEtc. 
*OpenAIRE: can adopt the guidelines, and propagate it to repositories. And to maintain the guidelines. 
 
- what would the work to be done look like
Communicate to all stakeholders in the world , this is IT! In the beginning, and in the end.Put online - hosted by SURFEditing partiesAgreed version 1.0 interoperable guidelines: eind of MAY 2010Agreed: = all the parties have the chance to contribute:Endorsement: OpenAIRE (EU), SURFsure (SURF), PIRUS-2 (JISC), OA Statistik (DFG), RePEC ()Beta Implementation starting in juneReviewing in September.Results in agreed version 2.0 (stable) 
- what would be required to make it happen
Writing of the guidelinesOnline environment6d for the work (2d for each project)2d overhead& coordination (Peter)1rst half of April: initial online document.2nd half of April: online meeting (Agenda)2nd meeting in 2nd half of MAY. After the meeting we have an agreed version 1.0Advocacy (conferences, etc.)Test Implementations (at each project, internally, not accross projects, yet)June till sept.Review (Face to Face in Sept. In the UK)Get one Base URL from each project , and test the interoperability , not setting up a service.!!!Resulting in an agreed version 2.0 

  • who are the actors/parties that should take part
    SURFsure (SURF)PIRUS-2 (JISC)OAStatistik (DINI)RePEcNEEOOpenAIRE 
  • in what way could Knowledge Exchange help further this activity
    Putting their stampFacilitate meetingsCommunication to all the stakeholdersOrganisational umbrella 
  • would it happen without KE
    We wouldn't be here if it wasn't for KEProject instigation/inspirationWe need to have a temporary "home" for this project, 
  • an indication of timeline and resources required
    Timelines are there - specific deliverable of each participating projectResources:Resources are already assigned from the originating projects, PIRUS-2, OAStatistik, SURFsure.OpenAIRE:Host the Guidelines and Maintain it.need to review the guidelines, and perhaps need some extensions (e.g. FP7 project number)RePEc & NEEO providing consultancy/review & endorsementKE: facilitates face-to-face meetings(What does that mean? Is it to FUND the meeting, so it does not take away project budgets?) 
    How will we communicate?
    Primarily by e-mailConf. call via "Powwownow", Skype or another virtual meeting technology 
    Edititng the guidelines
    The wiki is used to generate the firs draftThis is being distributed to all the participantsThey make their comments (with track changes ON)They send it back to the coordinatorThe coordinator is incorporating all the changes and is putting a new version online.In the first conference call, we discuss the latest version of the guidelinesA final round of changes is made to get all the changes, and then we have version 1.0We date stamp each wiki version (after each round)We can put this proposal in the wiki
  • No labels