BRII Meeting

Developer meeting should occur every third week of the month, roughly and SCRUM techniques should be put in place to follow up the projects more efficiently.

SCRUM is an Agile process that can be used to manage and control complex software and product development using iterative, incremental practices. Scrum has been used from simple projects to changing the way entire enterprises do their business. Scrum significantly increases productivity and reduces time to benefits while facilitating adaptive, empirical systems development.

 

Confusion/overlap of Sympletic and ORA, with possible project being left behind over the other. The ORA team will notify the ‘decision makers’ about the benefits of having ORA over the other platform.  Selling of ORA and its strengths compared with other management tools.

 

Still to check: Google API, Atom/RSS feeds.

 

To explore: IDs (yahoo/google) ==> profiles (BRII), maybe using the same id to enter in BRII???

 

There is a technical API workshop that will happen in July – date TBC.

 

Webpage/project researacherID (Neil Jacobs – web of science) – interesting use of IDs.

 

Items for the BRII bluepages:

  • include researcherID (pull info and populate record in BRII)
  • graphs of collaboration once is hover over the badge
  • quick, edit in place (Jquery)
  • way of informing the source of information (profiles) that there is a misspelling, an error, etc.
  • “zoom in – zoom out” tool:  the power to aggregate and disaggregate data (as it will be seen by its users)

BRII Meeting

Vocabularies (some in ns.ox.ac.uk)

Quality of data (for future bluepages):

  • flag problems with data (wrong spelling of name, etc)
  • one-button-form
  • compounded info (2 places) that can be tracked back
  • record of the source 9dept, person responsible, website, etc)

Some people offered data but it has to be analysed… if it is not good or not well formatted the data might not be taken into consideration and should be reported why.

Website ‘output’ RDF (medical sciences)

Widget to pull-out info from ORA (bibliography, for example) – Atom feeds.

Katie Portwin – specialist in RDF.

Mentioned:

  • Remembering what Themes are (“cancer”, “heart”, etc).
  • Spin-off ontologies
  • ICT project (check) – “people data”
  • Dlib journal id.lc.gov (digital links/linked data) – library of congress subject headings.

Oxford Digital Libraries (ODL)

The Oxford Digital Library has a major role in co-ordinating and stimulating digitization activities in the University.

Mike Popham has a background in English literature and then he went into digital preservation. One of the intentions within ODL is to have controll over the images and metadata associated to it, planning to manipulate/recover this information later on.

Green stone, an open source digital library, was used but stayed the same since 2005.

Some projects:

The Shakespeare project (EEBO) used SGML and then XML. ProQuest did the microfilming.

One of the questions on the ODL project is to add style to each library page; and this should be a corporate identity? or an unique style?