wiki:WikiStart
Last modified 11 months ago Last modified on 09/15/13 23:43:01

Welcome to Apidictor

Apidictor

is the wiki and task-tracking website of the Humanities Networked Infrastructure (HuNI) project. (An actual Apidictor is a device for monitoring and analysing the buzzing sounds of bees in a hive.)

In it you will find extensive information relating to the HuNI project. Read only access is open to everyone. Edit access is available to people who need it - if you're a partner of the HuNI project and wish to have an account on Apidictor, please email the site administrator, and please read the Wiki Guidelines before editing the wiki.

Whether you're a project member or not, you can stay up to date with news about HuNI.

For a complete list of Apidictor pages, see TitleIndex

Meta Table of Contents for Project Technical Information

About HuNI

HuNI is a NeCTAR funded project - one of the first large scale eResearch infrastructure projects for the humanities in Australia.

The project will integrate a number of important cultural data-sets in Australia and align them to a common ontology, store the data in a linked data store, and will also build what is termed a 'Virtual Laboratory' (VL). A VL is an online environment of tools and services to allow specialist researchers to come together to perform certain computational research tasks with the possibility of uncovering new insights and research into Australia’s cultural landscape.

The HuNI website offers further information about HuNI and its vision, how the project is being deployed (Project Management Plan), and details a list of relevant events: http://www.huni.net.au/

Project Governance

  • The Steering Committee provides the project with overall guidance and direction.
  • The Project Team oversees the planning, development, implementation, acceptance and evaluation of the all project deliverables and assets.
  • The LabDev group is responsible for overseeing the planning and development of the HuNI Lab (underlying technical infrastructure and user functionality).
  • The OntDev group is responsible for overseeing the development of the HuNI ontology).
  • The Technical Working Group is responsible for overseeing the development and implementation of the technical aspects of the data integration.
  • The Expert Data Group will provide input for the data mapping and ontology development.
  • The HuNI User Reference Group is being supported to ensure that HuNI Partners and peers, as users of the HuNI virtual laboratory, together with other potential users, drive the development of HuNI.
  • The HuNI Expert Advisory Group is providing international advice and validation, drawing on the expertise of a range of leading international experts.

The Project Directory will offer a full list of who's who, and who is represented on which governing or working group.

  • To find out what people are up to, see WorkSpaces.
  • To record your own ideas and look for opportunities to collaborate in writing and speaking spots in conference, journals, seminars etc, see ScholarSpace.

Project Infrastructure

Name Servers/Hostname WebApplications/Services
Corbicula corbicula.huni.net.au Linked data server
OAI-PMH Harvester

Technical and Semantic Interoperability

The system architecture is based on Linked Data. See the Glossary for an explanation of terms, and a list of related projects.

This site is currently hosted on a virtual machine called apidictor?, which lives in the NeCTAR Research Cloud. On the same VM there is a small demonstrator / proof of concept application.

The schedule for the semantic mapping and integrating the data sources has been re-sketched and the steps outlined. This is so planning around developing technical 'connectors' to the data sources and iteratively developing a core ontology (with reuse of components from other ontologies) can be managed with a wide group of project participants at different stages of development and readiness.

HuNI Asset Register

HuNI assets include:

  • Source code (java)
  • Compiled binaries (jar)
  • Packaged applications (war)
  • Web resources (html, css)
  • Image source files (ps)
  • Rendered images (jpeg, png)
  • Project administration documents (pdf)
  • Planning documents (pdf)
  • Conference presentation documents (pptx)
  • Servers and server instances/snapshots with associated credentials

Secondary assets are things such as document backups. We have a backup policy.

Virtual Laboratory (VL) Planning and Implementation

A user-centric approach to the development of the virtual laboratory is being deployed to ensure that its functionality and user interface design is developed in line with researchers' needs and expectations. Only then will the lab be open, adopted and supported by the communities it's designed to service.

The HuNI Agile Development Process has been defined, ensuring the functionality of the lab is tied to delivering the requirements described in the user stories.

The tool_implementation_strategy describes how the project is approaching the development and integration of tools into the HuNI lab.

The Product_Backlog is being produced which outlines a set of user stories that have been identified from interviews with scholarly researchers who are interested in using the HuNI lab. None are committed to being worked on, and each is given an importance rating. The HuNI Steering Committee will prioritise the stories and select those for implementation.

Please see Virtual Laboratory for more information about the virtual lab and tool analysis and design:

Datastore Planning and Implementation

Commonly call the HuNI Aggregate this is built by a process of data extraction, filtering, transformation and versioned publication by HuNI data providers and subscription, transformation and ingestion by the HuNI organisation. The system architecture is the centre point of the planning. A convienient starting point is the Datastore table of contents .