the duraark workbench and premis
DESCRIPTION
Pre-Ingest workflows are comparatively new to the digital preservation domain – while the main focus of earlier efforts has been put on the needs of the organization / the repository which is responsible for the long-term stewardship of objects, questions around earlier processes have been arising only recently. Due to this “pre-ingest” dependencies and implications are not explicitly covered in standards like the OAIS or in PREMIS. The question is how information about the external pre-ingest service can be described meaningfully to the repositories and what level of granularity is called for. The DURAARK project has explored this subject with a planned PREMIS implementation in the DURAARK workbench, which covers pre-ingest tasks for architectural 3D data. The presentation highlights 3 central questions that arose in connection to the PREMIS implementation.TRANSCRIPT
10 / 06 / 14
The DURAARK Workbench and PREMIS
Michelle Lindlar (LUH / TIB)
PREMIS Implementation FairMelbourne, October 6th 2014
10 / 06 / 14
DURAARK (DURAble Architectural Knowledge)FP7 – ICT – Digital Preservation (STReP)February 2013 – January 2016
GoalDevelop methods and tools for digital preservationand curation of 3D building data
Scope• interlinked curation and preservation workflows• focus on two open file formats:
IFC and E57• incorporate results into an existing
OAIS compliant digital preservation system (= TIB’s dps) – but also enablewide adoptability of results amongststakeholders
Project overview
10 / 06 / 14
DURAARK – an interdisciplinary project
10 / 06 / 14
3D building data – scans
ScanCoptor by FaroLabs
Point clouds
Point clouds are a set of points in a 3D (X, Y, Z) coordinate system which describe the externalsurfaces of a scanned object.
While other domains may use post-processedNURBS models or 2D slices as the 3D scanreconstruction, the architectural and construction domains work directly with point clouds.
E57 – ASTM E2907-11 Standard
Zebedee by CSIRO
10 / 06 / 14
3D building data – models
Building Information Modelling (BIM)
Moves beyond CAD by covering the entire design-to-construction process (including: project planning, cost, part specifications, construction time, …)
IFC – based on STEP standards (ISO 10303), ISO16739:2013
3D CADGeometry along X-Y-Z axes
4D CADSchedule time
5D CADCost-related information
6D CADEnergy and sustainability
7D CADFacility management
Lund Cristallen by DURAARK partner CCO architects
10 / 06 / 14
Use cases
Class 1: System processes- Deposit 3D architectural objects- Search and retrieve archived objects
Class 2: Semantic Digital Archive - Maintain the semantic digital archive (SDA)- Enrich BIM model with metadata from SDA
Class 3: Curational use cases on the geometric level- Detect differences between planning and as-built state- Monitor the evolution of a structure over time- Identify similar objects within a point-cloud scan
Class 4: Curational use cases on the semantic level- Plan, document and verify retrofitting/energy renovation of
buildings- Exploit contextual information for urban planning
10 / 06 / 14
Input: point clouds in file format E57
Building Information Models in IFC
DURAARK Workbench
10 / 06 / 14
Output: METS + PREMISIFC, E57, IFCowl, IFC2PC.rdf, …
DURAARK Workbench
10 / 06 / 14
The DURAARK workbench …… is a pre-ingest workbench with no knowledge of the digital preservation
system / repository which the SIP will be deposited to
Question regarding PREMIS:Per design PREMIS is repository centric and built on repositoryrequirements. In the case of the generic pre-ingest workbench whichproduces PREMIS data, the role is unclear. Should the pre-ingestworkbench consider itself the repository and the transfer to the digital preservation system / archival storage is „inter-repository exchange“ ? Orshould the pre-ingest workbench leverage provenance data, e.g., byconsidering itself an agent and capturing this information ?
PREMIS questions
10 / 06 / 14
The DURAARK workbench …… is a repository external system (an agent ?) and wraps several tools (e.g.
DROID for file format identification as well as DURAARK tools).
Question regarding PREMIS:The workbench may be considered an agent - the tools it wraps arecertainly agents. For transparency, agent information should be capturedin the PREMIS data, especially since it‘s a repository-external process. How can this be achieved if both – workbench and tools – are agents ? Canagents be represented in an encapsulated manner in PREMIS ? Or is theworkbench the overarching agent responsible for producing the PREMIS metadata itself?If the latter – is it common / (allowed?) to have an eventType=creationfor the PREMIS file itself ? Or is that a hen-egg problem ?
PREMIS questions
10 / 06 / 14
The DURAARK workbench …… sees „a building/strucutre“ as an Intellectual Entity. Plans / scans which
describe thie IE always have temporal / spatial dependencies and cantherefore not be considered on the same representation level, but shouldrather be handled as sub-IEs.
Question regarding PREMIS:Per data dictionary PREMIS allows encapsulated IEs: „An IntellectualEntity can include other Intellectual Entities; for example, a Web site caninclude a Web page; a Web page can include an image“. However, no reference implementation / example could be found. What is the statusof this ? What is the impact on the implementation ?
PREMIS questions
10 / 06 / 14
Summary of questions:
1. Pre-ingest workbench as agent orrepository or … ?
2. If agent, how and where to capture this ?
3. Encapsulated IEs?
Any answers, experiences, comments, thoughts, questionsare welcome !
Summary
