Get Started. It's Free
or sign up with your email address
Rocket clouds
Jerome by Mind Map: Jerome

1. Analytics on data use

1.1. G Analytics

1.1.1. Site search - how do search terms lead to content? Paths.

1.2. API logs

1.3. Using external analytics to teach jerome?

1.3.1. MOSAIC

1.3.2. circ_tran

1.3.2.1. Can we compare J searches to subsequent checkouts?

1.3.3. G Analytics on HiP etc

1.4. Social media - embedding

2. Openly licensed, bibliographic data

2.1. MARC records

2.1.1. COMET: Identify ownership.

2.1.1.1. Records with no ownership problems

2.1.1.1.1. MARCXML

2.1.1.2. Look at Cambridge tool for identifying.

2.1.2. We need a meeting with the cataloguers!

2.2. IMPORTANT: Jerome can link to the original (HiP display, EPrints) but will serve up its own "new original".

2.3. EPrints data

2.3.1. "Download this record"

2.3.2. Create list to download

2.3.3. Download all?

2.3.4. Records with third-party ownership problems

2.3.5. Licence: "The metadata may be re-used in any medium without prior permission for not-for-profit purposes and re-sold commercially provided the OAI Identifier or a link to the original metadata record are given." --- where's the comma? CC-BY? CC0?

2.3.5.1. Would the university insist on attribution? Ask Ian.

2.3.6. What format is the original data in? EP3 Dublin Core XML

2.4. A-to-Z knowledgebase

2.4.1. No. EBSCO own the data.

2.4.2. Include LoC headings

2.4.3. Provide attribution to EBSCO

2.5. Journal TOCs

2.5.1. No. Using them under CC-BY licence. Check! Ask HW about their CC-BY licence. Internal usage only?

2.5.1.1. Can we harvest?

2.5.1.2. Can we distribute under CC-BY

2.5.1.3. Does the CC-BY cover the API, or the source data?

2.5.1.4. What about commercial interests?

2.5.1.5. Ask JISC OBD

2.5.2. Rely on notice and takedown?

3. Attractive, documented, supported APIs

3.1. Bibliographic APIs

3.1.1. Any item, search result or browse view is available. (append URL with .format)

3.1.1.1. XML

3.1.1.1.1. RSS

3.1.1.1.2. Full "native" XML

3.1.1.1.3. RDF

3.1.1.2. JSON

3.1.1.3. BibTeX

3.1.1.4. XBEL

3.1.1.5. csv

3.1.1.6. MARC

3.1.1.7. RIS

3.1.1.8. Text citation

3.1.1.9. !!! Sort out format vs delivery!!!

3.1.2. "New additions" API

3.1.2.1. "First noticed" field?

3.1.2.2. Visualisations

3.1.2.3. RSS

3.2. Item APIs

3.2.1. JSON

3.2.2. RDF

3.2.3. RSS?

3.2.4. Enrich Horizon content with Nucleus/external? data

3.3. User APIs (out of scope)

4. A sustainable public-facing search portal

4.1. "Send to..."

4.1.1. RefWorks

4.1.2. Social media

4.1.3. Kindle?

4.2. Record enrichment

4.3. Lists

4.4. Logging in

4.5. Recommendation engines

4.5.1. Weighting. Look at Dave P's stuff

4.6. Mixing desk

4.7. Machine-readable

4.7.1. COinS

5. A semantic sitemap of aggregated data

5.1. Find out what Joss meant by this.

6. Documented technical user case studies

6.1. Write developer case studies - what form should these take?

7. Documented ‘user journeys’ case studies

7.1. Write user case studies - what form should these take?

8. Documented use of infrastructure

9. Documented machine learning/personalisation engine

9.1. Document use of Neo4J and machine learning algorithms

10. Contributions to community events

10.1. JISC Infrastructure for Resource Delivery meeting, 1 March, Birmingham

10.2. Mashed Library, 8 March, Lincoln

10.3. Personalised Library Services, 22 March, Cambridge

10.4. cpd25 mashups workshop, 13 April, London

10.5. Opening Data, Opening Doors, 18 April, Manchester

10.6. UC&R Yorks & Humberside event: Discovering Discovery Tools, 16 May, Huddersfield

10.7. Discovery - building a UK metadata ecology, 26 May, London

10.8. Cambridge hack event???????????????????????