A presentation given by Stephen Woodruff, a Resource Development Officer in the College of Arts at the University of Glasgow.
The presentation was made at the 'Managing Archaeology Data and Documentation' event on Monday 7th march.
Overview of a Technical Appendix will draw upon examples of successful bids
others in Hatii and in English Language. We work as a team – likely to pass the buck if you ask a question
NERC = Natural Environment Research Council ESRC = Economic and Social Research Council These require data management plans, which are one component of a technical appendix Small websites that serve only to provide information about a project are exempt, but fairly rare (your research outputs are likely to be delivered in some digital form)
Work in Word to check character count and avoid Je-S website TIMING OUT I’ll use the standard AHRC technical appendix format to structure this short talk, but the points raised should be relevant to any funding application that includes a digital output.
Reporting structure, division of responsibilities, deliverables File formats, documentation Technical expertise, hardware/software/training requirements Advice sought on preserving access to the data, sustainability & 6. Are smaller sections that I’ll cover shortly
- So you may omit non-technical responsibilities - Especially highlight members of proposed steering committee with technical expertise - ‘Management & reporting Structure’ is one of the longest sections (2000 characters)
Planning = requirements capture, looking into the current state of things Evaluation = testing. Bear in mind that those closest to the project will feel most at home working with its outputs. You’ll know how to get the best out of your own research data!
d. Again, focus on the technical expertise in your steering committee. Likewise, if your PI or Co-I(s) have technical backgrounds, their explicit contribution to the monitoring process might be explained
Stress that the PI/researcher will work closely with the technical people on this to ensure that content created is both intellectually sound and technically appropriate
The Dublin Core set of metadata elements provides a small and fundamental group of text elements through which most resources can be described and catalogued. Using only 15 base text fields, a Dublin Core metadata record can describe physical resources such as books , digital materials such as video , sound , image , or text files, and composite media like web pages .
e.g. HATII and its reputation for research in the area of digital curation and membership of organizations such as the DCC HATII’s previous projects include Mapping Sculpture, theGlasgowStory, the Whistler project, etc…
Examples: server maintenance, set-up of project workstations and laptops, RAID-5 disks configurations, SAN Mobile example for new hardware
VADS = visual arts HATII also partners in DCC, OPF, DPC AHDS = Arts & Humanities Data Service
Circumstances: personalisation, user generated content Testing = usability, widening access
Database right: originality in the selection of the contents and the result of substantial investment
Research: digital curation, web technologies, digitization Examples: Mapping Sculpture & PLANETS (15 million euro)
![Providing technical support during research projects ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)