1 / 18

M2LD and the Research Project Lifecycle

M2LD and the Research Project Lifecycle. From Metadata to Linked Data Jennifer Edmond. Where we ended…. What to model? What to link? Digital rot? …all questions gesturing toward the link between technology and the research process. The very big question.

ghada
Download Presentation

M2LD and the Research Project Lifecycle

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. M2LD and the Research Project Lifecycle From Metadata to Linked Data Jennifer Edmond

  2. Where we ended… • What to model? • What to link? • Digital rot? • …all questions gesturing toward the link between technology and the research process

  3. The very big question How do we get the most out of the (often sizable) investment of time, money and intellectual input that we make in a digital humanities project?

  4. Levels of knowledge Known Known Unknowns Unknowable Knowns Unknowns Unknowns Unknowns Research Technology Standards Migration Questions Choices Metadata Technology Dissemination Choices

  5. A few more questions What do you need to know for scoping (best practice, similar projects, reusable tools)? What skills or collaborators (=resources) do you need for delivery? What time or equipment (= more resources) do you need for delivery? Remember: more projects fail because of planning than technical barriers (the old trilemma of good/fast/cheap)

  6. Distinct array of skills required • Humanities domain knowledge • Technical design • HCI • Data architecture/knowledge engineering • Process • Control • Environment

  7. Research as sigmoid

  8. Longer term perspective project hand-over pro-posal plan idea

  9. Where the support is project hand-over pro-posal plan idea

  10. A single project Inter-pret dissem-inate assem-ble gather prep

  11. XML markup (Oxygen) Parallel Markup Geospatial markup (kml, Google Earth) Versioning Machine Collatex Juxta TaporWare Voyeur OpenCalais Yahoo Pipes OWL Ontologies (Protégé) Sparql Queries (Snorql)/RDF/TTL

  12. Where are the possible connection points between these technologies/tools and the research process? imagine, design, build, investigate, document, maintain, migrate

  13. A single project Inter-pret dissem-inate assem-ble gather prep

  14. Case Study Framework • What are the research questions and/or those of the intended users? Can/should other possible future users be taken into account? • Does the research project have the resources it needs (team/skills/money/time)? • Where in the research process is there a role for M2LD technologies? Which ones? • What are the scope/resource implications of this adoption (in the short and long term)? • How well integrated into its environment is the project? • Who are its stakeholders, and are they engaged? • Does the project need to raise/lower its ambitions to be deliverable?

  15. Case Studies • 10 minutes: Intro, shuffle, elect rappoteur (not the case owner) • 10 minutes: read/review case study • 10 minutes: questions to case owner • 20 minutes: discuss within case study framework, in particular how various technologies *could* be implemented and whether they *should* be used (but don’t feel limited to this) • 10 minutes: assemble report Coffee at 11!

More Related