So#waretechnologie für Fortgeschri4ene Teil Eide. Stunde III: Modellierung

Transcription

1 So#waretechnologie für Fortgeschri4ene Teil Eide Stunde III: Modellierung (with contribu>ons from Chris>an-Emil Ore, Jon Holmen, and other colleagues at the Unit for Digital Documenta>on, University of Oslo and from Mar>n Dörr and Stephen Stead, CIDOC-CRM SIG) Köln 15. Dezember 2016

2 Overall architecture online offline Client Client Media-server diskraid tapesta1on Client Client

3 Data flow Client Request to store media file, (filename+path, user, topnode, process-xml) Mediaserver returns a pointer to the mediafile hub Media-server Based on user, format, topnode, Media-server validates, stores file, and parses the process-xml to create requested new versions diskraid

4 Towards abstract modelling How can this method be generalised? Some preliminary notes Learning strategies The role of theory theory/modelling implementa>on

5 What is an image? An image can be found in a data file on a 35mm film at a paper posi>ve at a glass plate We do not care, they are all images modelled as media_units connected to media_groups If something is another media_unit to an exis>ng media_group, or a derived media_group is a scholarly (content based) choice

6 The transforma>on event Each transforma>on event happened in >me may or may not know when actor(s) may be know or unknown Transfer events from analogue to analogue analogue to digital digital to digital (digital to analogue) are recorded in the same way

7 Chains of events Connected to a image there is a chain of events like the passport of a person with stamps Can see where the image comes from Can step in at any point to re-do processing Some images can be seen as caches but the dis>nc>on between cached and not is not central rather: some processes can be re-done but be aware of detail differences program versions libraries

8 The memory of events Storing events: wri>ng history This is obviously important for old stuff museums try to track provenience But all new will become old History is made by our scripts we can record it or let it go

9 Reminder: Event centric data model source à recording à result Media object Types External Analogue nega>ve Analogue posi>ve Digital photo Digital copy. Source of Event recording Types Photographing Repro Copying Scanning Results in when performed by where Media object Types Analogue nega>ve Analogue posi>ve Digital photo Digital copy. Time span Person Place

10 Reminder: Data model (example) Separa>on between informa>on object and informa>on carriers discipline cataloguing discipline cataloguing media_group (informa>on object) Is carrier of media_unit a nega1ve film media_unit b paper posi1ve media_unit c file from scanner Event 1 Camera, 1966 Event 2 Copying,? Event 3 Scan, 1997 media_unit d file Event 4 Resizing, 2004

11 Remember: Database Discipline schema 1 image_card media_group_id concent_metadata subject specific tables Common schema media_group id process_xml tech_metadata media_unit tech_metadata default {0, 1} schema_setup process_spec delete_limit process process_spec status {0, 1, 2, 9} Discipline schema 2 image_card media_group_id concent_metadata subject specific tables

12 Which discipline?

13 Which discipline?

14 Which discipline?

15 Which discipline?

16 Iden>cal photographs?

17 Which discipline?

18 Which discipline?

19 Which discipline?

20 Event centric data model Media Object A Type: Digital copy Skrik Source for Event Media Object D Media Object B Source for Type: Use of photoshop Results in Type: Collage The Imsdal man Meets Munch Type: Digital copi: The Imsdal man when Performed by when Timespan Person Place

21 Date model, concepts and things Conceptual object Media group -unit A Informa>on Object Skrik Media group - unit B Informa>on Object Media Object A Type: Digital copy Media Object B Type: Digital copy Based on Media Object C Type: Digital copy Conceptual object Media group -unit C Informa>on Object The Imsdal man Meets Munch The Imsdal man Physical thing

22 Model of vs. model for

23 Modelling strategies: examples Modelling for produc>on Computer science e.g. UML Digital Humani>es e.g. TEI Modelling for understanding Digital Humani>es (Humani>es, natural sciences, ) Modelling for data integra>on Computer science e.g. Seman>c Web Digital Humani>es e.g. TEI Cultural heritage e.g. CIDOC-CRM

24 Introducing CIDOC-CRM Historical Archives Type: Text Title: Protocol of Proceedings of Crimea Conference Title.Sub1tle: II. Declara1on of Liberated Europe Date: February 11, 1945 Creator: The Premier of the Union of Soviet Socialist Republics The Prime Minister of the United Kingdom The President of the United States of America Publisher: State Department Subject: Postwar division of Europe and Japan Metadata Documents About The following declaration has been approved: The Premier of the Union of Soviet Socialist Republics, the Prime Minister of the United Kingdom and the President of the United States of America have consulted with each other in the common interests of the people of their countries and those of liberated Europe. They jointly declare their mutual agreement to concert.and to ensure that Germany will never again be able to disturb the 24 peace of the world

25 Type: Image Title: Allied Leaders at Yalta Images, non-verbose Date: 1945 Publisher: United Press Interna1onal (UPI) Source: The Be`mann Archive Copyright: Corbis References: Churchill, Roosevelt, Stalin Photos, Persons Metadata About 25

26 Places and Objects TGN Id: Names: Yalta (C,V), Jalta (C,V) Types: inhabited place(c), city (C) Posi1on: Lat: N,Long: E Hierarchy: Europe (con1nent) < Ukrayina (na1on) < Krym (autonomous republic) Note: Site of conference between Allied powers in WW II in 1945;. Source: TGN, Thesaurus of Geographic Names Places, Objects About Title: Yalta, Crimean Peninsula Publisher: Kurgan-Lisnet Source: Liaison Agency 26

27 The Integration Problem (1) Problem 1: identification of things Actors, Roles, proper names: Places Events The Premier of the Union of Soviet Socialist Republics Allied leader, Allied power Joseph Stalin. Jalta, Yalta Krym, Crimea Crimea Conference, Allied Leaders at Yalta, conference between Allied powers Postwar division Objects and Documents: The photo, the agreement text 27 27

28 The Integra4on Problem (2) Problem 2: hidden (implicit) entities (typically under title ) Actors Allied leader, Allied power Places Yalta, Crimea Events Solution: Crimea Conference, Allied Leaders at Yalta, conference between Allied powers Postwar division Make better metadata structures: but what are the relevant elements? 28 28

29 Explicit Events, Object Identity, Symmetry E39 Actor E52 Time-Span February 1945 P82 at some within time E7 Activity P7 took place at E53 Place E39 Actor E39 Actor Crimea Conference P86 falls within E65 Creation Event * P81 ongoing throughout E52 Time-Span E38 Image E31 Document Yalta Agreement

30 The Intellectual Role of the CRM Conceptualization? approximates explains, motivates Data structures & Presentation models organize World Phenomena 30 Data bases Legacy Legacy systems systems Data in various forms

31 Top-level classes useful for integration E55 Types E41 Appellations refer to / identify refer to / refine E28 Conceptual Objects E39 Actors E18 Physical Thing participate in affect or / refer to location E2 Temporal Entities E52 Time-Spans within at E53 Places 31

32 Event centric data model Media Object A Type: Digital copy Skrik Source for Event Media Object D Media Object B Source for Type: Use of photoshop Results in Type: Collage The Imsdal man Meets Munch Type: Digital copi: The Imsdal man when Performed by when Timespan Person Place

33 Visual Content and Subject E24 Physical Man-Made Thing P128 carries (is carried by) P62 depicts (is depicted by) P62.1 mode of depiction P67 refers to (is referred to by) E55 Type E1 CRM Entity P65 shows visual item (is shown by) E73 Information Object P138 represents (has representation) P138.1 mode of depiction E84 Information Carrier E36 Visual Item E38 Image 33 E37 Mark E34 Inscription

34 Date model, concepts and things Conceptual object Media group -unit A Informa>on Object Skrik Media group - unit B Informa>on Object Media Object A Type: Digital copy Media Object B Type: Digital copy Based on Media Object C Type: Digital copy Conceptual object Media group -unit C Informa>on Object The Imsdal man Meets Munch The Imsdal man Physical thing

35 Development and modelling theory/modelling implementa>on

36 Sessions 24. November 1. December Cancelled, but see below 8. December 15. December Monday 23. January Paul Fishwick: guest lecture 26. January 2. February (9. February)

37 h4ps://