User Manual
Contents
1. 7 Zee Describing detalls or am 7 2 3 Describing the input of a Process Event eene 7 2 3 1 All input files should be 6 7 2 3 2 Introduction of intermediate files ccccccccssssscecccesseceecceeeceecseueeeesseeeecessaeueeeessaeaeeeessegaeeesseees 7 2 3 3 Some process events may not have input 65 9 2 4 Describing the documentation of an 9 2 5 Asynchronous and 5 5 9 3 5 10 3 1 Ee Tete T m mm mn 10 32 Handling an Event ES 11 3 3 ACOHISICIODHBVETTU ossi iens E tom petia T ome EE Ere E ee 12 3 3 1 Output Dieital OBJEC PNIS 12 3 3 2 ACUO E VONE se2. New event Operato Te j J New Update event Person Days Load event templa Save event template Inaestto RI Project 2012 08 10 project Byzantino Pending Uploads Start date 2012 08 10 yyyy mm dd hh mm End date yyyy mm dd hh mm Event 2012 08 10 process Figure 24 Form for editing the description and details of the process that produces the intermediate files 21 3D 2Y2TEK n Reposit Tool Event title 2012 08 10 proces IMProcess uuid a8 Soflware Software Parameters Parameters file Organization 4X 770008 New event Update event Load event templa Save event template Inaestto RI Project 2012 08 10 project Byzantino Operator Person Days Start date Event 2012 08 10 Other title Type Enddate Help About Output digital objects Process event Input digital objects Documentation 2012 08 10 Cs DIET Edit New Browse l r Edit i New Edit New 2012 08 10 yyyy mm dd hh mm yyyy mm dd hh mm Pending Uploads Figure 25 Form for selecting the input of the intermediate files generating process The left scrollbar displays the events that are currently described during one event description enabling the user to jump from the one process event to the other Thus as shown inFigure 26 once the user has finished
3. Reposit Tool Help About Output digital objects Acquisition event Setup amp Devices Documentation Event title 2012 08 10 non portable device scanning Othertitle Untitled Type port v j f ble devi i i 2012 08 10 non port Oa non able device scanning Edit 5 portable device scanning ss _ e Operator x j Edit New a Person Days Start Dates 2012 08 10 yyyy mm dd hh mm Li 4X 7 yr ov End Date yyyy mm dd hh mm Neweven caLocation I jJ L New Update event i Acq Object L texture Edit New Load event template MC Description Save event template Ingestto RI Project 2012 08 10 project Byzantino Event Untitled Pending Uploads Figure 10 Form for editing the description and details of an acquisition event The user can specify a value in a field e g Operator by selecting a value from a drop down list of values from the RI This list also enables type ahead and use of sub strings for narrowing the selection of available values from the drop down Type ahead search activated after typing at least three characters Fields with on their labels are obligatory Fields in grey are not editable These may be fields that their value is calculated by the values of other fields Such fields are the Event title fields e g an acquisition event title is calculated by the Event type date museum object etc This calculation mechanism
4. already ingested in the repository as mentioned earlier can also be the product output of another process for which the user decided that was not needed and was erased see Figure 1 process B output In this case the Reposit Tool assists the user in describing the metadata for this process too process B describing the software and the parameters used up to the files used as input already in the repository 3D 2Y2TEK Process A output Data files specified as on the disc UUID Data files Ingested in the RI Figure 1 Intermediate files maybe created between two processes This way the tool provides referential integrity when describing a chain of processes which intermediate data are erased We will hereafter reference these products as intermediate files The tool considers for simplicity reasons the intermediate files between two process as one file see Figure 2 intermediate files between processes B and A generating only one UUID for this intermediate data Figure 2 Intermediate files between processes are concidered as one file The metadata generation in the case on intermediate files between multiple processes include the description of all the processes up to the input files of the first process see Figure 2 the upper green cloud denotes the generated metadata for both process C and process B it will be ingested with the output data file of process C 3D 2Y2TEK 2 3 3 Some p
5. Figure 6 Adding a new Project description In all forms at the left bottom area the following functions are available Figure 7 e New event Update Event e Load event template e Save event template e Ingest event to RI 11 3D 2Y2TEK S Reposit Tool Help About Output digital objects Acquisition event Setup amp Devices Documentation Eventtitle 2012 08 10 Other title Untitled 4 Type v I a 2012 08 10 Organization Edi New i Operator 4 Edit New a Person Days il Start Date 2012 08 10 yyyy mm dd hh mm L v End Date yyyy mm dd hh mm ma Acq Location Edit New Update event n Acq Object texture Edit New M Load event template A Description Save event template Ingestto RI Project 2012 08 10 project Byzantino Event Untitled Pending Uploads Figure 7 From the left bottom area of main form the user may create a new event load and save events to disc and ingest an event By pressing button New event the user may choose create a new event If the button is pressed while editing another event the user is prompted to save or discard the current event By pressing button Update event the user may choose update an existing event If the button is pressed while editing another event the user is prompted to save or discard the current event By pressing bu
6. a which data were produced b by what procedure c using what input and probably d with some form of documentation in needed to be declared 2 2 Describing details of an Event The user describes events either acquisition events or process events For each event the user should specify attributes concerning the event itself specifying 7 the title of the event the time the event took place m the place the event took place the organization the operators actors involved in the event etc For the description of an acquisition event the user should also specify the devices or software used for the acquisition some information on the acquisition setup and if necessary device calibration information For the description of a process event the user should also specify the software used for processing their input data the type of the software and the parameters used for the processing 2 3 Describing the input of a Process Event For a process event the user should also describe the input data he she used for processing 2 3 1 All input files should be already in the RI The tool does not allow the selection of data files that are not already ingested in the repository This ensures data referential integrity This also forces the user to first describe acquisition events and the subsequent process events which is only logical 2 3 2 Introduction of intermediate files The input except of being a set of data objects
7. arose from Deliverable 1 1 We present the basic supported event based functionality Support of the ingestion of data of a simple acquisition process It provides an automatic way to create the metadata files of an acquisition process providing the user the appropriate form s to assign metadata information on the acquisition event identification information of the depicted object and general acquisition setup and capturing device s information Support of the ingestion of data of a simple data processing procedure It provides an automatic way to create the metadata files of a data processing procedure providing the user the appropriate form s to assign metadata information on the processing event Involved partners should identify the required metadata for describing S W and S W versions along with the parameters that are passed to the specific S W There is no limitation to the number of independent acquisition processes and subsequent processing steps ingested individually but contributing to one or more 3D Models Mechanisms that assist in the ingestion of metadata information of intermediate processing steps that users decide to store in the repository hereafter RI while their intermediate data files are lost or erased Unified URI policy definition Full referential integrity control mechanism All forms interact with the RI and get information from it which is selectable by the user Thus there are no misspellings nor
8. city town village Broader area province country Figure 30 Form for creating a Place Examples of geonames ID or GeoNameld For the town Athens in Greece we have these two URIs 1 http sws geonames org 264371 2 http sws geonames org 264371 about rdf How to find a PLACE To find the GeoNameld through the geonames link of a place you can issue the following query substituting PLACE with the place name you are looking for e g Athens http ws geonames org search type rdf amp q PLACE r Create update building or exhibition space Pile Building Exhibition space name Place Edit New Address Apply Figure 31 Form for creating updating a Building Exhibition Space B create update Coordinates x Location Title Longitude x Latitude y Place Address Figure 32 Form for creating updating a Location by coordinates 24 Figure 33 Form for editing software Figure 35 Form for creating updating a Physical Object 25 3D 2Y2TEK 3D 2Y2TEK 3 6 Form Input fields functionality The forms of the Reposit tool have input fields like those shown in Figure 38 3 6 1 Input field functionality The user can either select a value from the drop down list or start typing in and the RI is queried for similar strings of the specific type Type ahead in input fields narrows the selection of available values from the drop
9. down list By typing in the input field the available values that match the typed string are narrowed see Figure 36 Important notice due to extremely long lists of available values the type ahead mechanism is enabled after typing at least three characters This mechanism uses Lucene engine for optimized queries Organization FORTH a zh Operator chr f eat New is Georgiou Start Date Christos Georgis Cryyy mm dd hh mm Jahn Chr ysakis End Date yvy y mm dd hh mm Figure 36 Input field type ahead use example Notice that fields in grey are not editable and that fields with on their labels are obligatory 3 6 2 Multi valued Input fields In some input fields the user can specify more than one values By selecting button a form will appear see Figure 37 In this form the user may add more than one value more than one Organization Person etc Add edit multiple values for Person Apply selected Operator Chris Geor1 New Figure 37 Multi valued Input field use example 3 6 3 Creation and update of entities The user can also insert new entities such as new Persons or update entities only those created using the Reposit Tool by selecting New or Edit button respectively see Figure 38 Then a form for introducing the new entity pops up to provide all the details of the entity Organization New Operator f Edit New gt Figure 38 Input
10. illegal cross referencing forms may be saved and re loaded for further editing This enables the user to revise the metadata before committing in the RI by using event templates Generation of zip files before upload for convenience usage and better file usage Asynchronous or synchronous ingest upload of all data and metadata in the RI for gaining better performance Auto re upload feature for incomplete files Information and Resuming of pending files 3D 2Y2TEK Type ahead search at all fields for easy access to the ingested entities digital objects of the repository Rollback mechanisms for corrupted event or files and auto switching to update mode if part of event has been ingested before a failure happens i e network failure Logging of SPARQL queries for further use of other related applications 1 2 Motivation The tool aims at ingesting legacy data concerning digital provenance information and data produced with tools that 3D SYSTEK has no implementation control over them thus cannot be integrated to the RI It is also provided to assist the ingestion of some bulk data in order to populate early the RI It is not provided to substitute the required integration of 3D tools with the RI We strongly believe that the tools integration with the RI can only be achieved by having each tool ingesting and retrieving to and from the RI without having an intermediate tool the Reposit Tool assisting the us
11. this information and pressing OK the initial form of tool is displayed The URL could be a list of URLs as denoted at the tool properties file see at Appendix If ticked the Remember me option in the next run of tool these elements are restored by the system In case of unsuccessful connection an alert message is displayed see Figure 4 URL User Password Remember me ERROR rcerr 51 Send soap request problem caused by Connection refused connect Please check your login elements and properties file or try later Figure 4 Unsuccessful connection error message 10 3D 2Y2TEK 3 2 Handling an Event description 59 3D Reposlt New oose action Ch e action Create new acquisition ewent Figure 5 Initial form of Reposit tool By invoking the tool the user may load an existing event description create a new one or update an existing one Each event is described within the framework of a project see Figure 5 The user may select an existing project or create a new one by pressing the New button A pop up form for introducing the new project see Figure 6 appears for the user to provide all the details of the project Create update project event B prne Title Project Title Contractor Edit New Owner Client i Edit mew Start date tyyyy mm dd hh mm End date yyyy mm dd hh mmj Mate
12. which loads at each run at the beginning of the Reposit Tool Below we present a common example of this file The property urls specifies the URLs comma separated URLs of the RI to be connected to e g http testserver SYSTEK ObjectRepository svc http 139 91 183 45 8080 SYSTEK services RIWS w sdl The property deletefiles if set to no allows the user to review the generated RDF metadata files The property instructs the tool not to delete the generated RDF files after ingestion completion These files are located in the RDFS folder of the tool The property querylog if set to yes allows the user to review all executed queries their results and their execution time and is used for debugging purposes All this information captured in a file named queries txt inside the RDFS folder The property sync if set to yes enables synchronous uploading of data and metadata Also the user has the ability to initialize entity combos by setting corresponding variables in the properties file with a specific regular expression pattern for each specific entity combo The regular expression pattern syntax follows the java regex format for more details see http docs oracle com javase 7 docs api java util regex Pattern html and is case insensitive The values of the following example properties file are identical to the default ones That means that if we don t set them or omit some of them the combos would be initialized by
13. with describing the new process can go back and review or continue the description of the first process by selecting the process name title on the left scrollbar S Reposit Tool EXIT Help About IMProcess uuid 38 2012 08 10 proces New event Update event Load eventtempla Save event template Ingestto RI Project 2012 08 10 project Byzantino Event 2012 08 10 processing Output dta one input oa onjedis Select digital objects from the repository Clear selected Query 107 asc of 2009 05 12 capture Eastern Moat Chania city walls 107 asc 107 blk of 2009 05 12 capture Eastern Moat Chania city walls 107 blk 107 jpg of 2009 05 12 capture Eastern Moat Chania city walls 107 jpg 108 asc of 2009 05 12 capture Eastern Moat Chania city walls 108 asc 108 bIk of 2009 05 12 capture Eastern Moat Chania city walls 108 bIk 108 jpg of 2009 05 12 capture Eastern Moat Chania city walls 108 jpg Selected intermediate files from process Describe earlier intermediate process IMProcess uuid 3854499e 6d71 42cf 9cdd e61b550bf337 L J _ No input required Pending Uploads Figure 26 Updated form with selected input file uuids or process output of a process event 3 4 4 Documentation In documentation tab the user can describe in a field the setup of the whole process and include ingest related documentation files for example photos vi
14. 3D SYSTEK Reposlt User Manual Version 3 4 0 a fee E Be AS V east eee S EZ LE A A USA TEE Authors Christos Georgis georgis ics forth gr loannis Chrysakis hrysakis ics forth gr Foundation for Research and Technology Hellas FORTH AA m w 2007 2013 eo m z z BB UTTTLELZLE EN KEVTHPO THS EYAE ETAK E N 3D 2Y2TEK 3D 2Y2TEK Table of Contents T Doduo ER 5 1 1 Functional T 5 1 2 6 2 Workflow Considerations esesssssssseseosesessssseosessssoeososessosseseosessosseosesesscssssosesessoeoe 7 2 1 Describing the output of 8
15. deo of the setup and possible documents with details on the setup installation by clicking the button Browse see Figure 27 22 3D 2Y2TEK Boo Goo cp HERR S Reposit Tool 2012 08 10 proces Documentation file s set_info pdf NEW FEATURES ht r New event Update event Load event templa Save event template Inaestto RI Project 2012 08 10 project Byzantino Pending Uploads Event processing Figure 27 Documentation tab for process event 3 5 Forms for the creation and update of entities Help About The user can also create new entities such as a new Person new Legal Body new Software new Place etc in the RI by New button or update existing entities in the RI by Edit button in forms described above A pop up form appears for introducing the new entity or for updating the existing one for the user to provide all the details of the entity see figures Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Ce RN NN EE EEE Last name URI Member of v Edit New 15 Figure 28 Form for creating updating a Person J Create update legal body a ba Legal body name Established in 7 j Edit New Apply Figure 29 Form for creating updating a Legal Boby 23 3D 2Y2TEK Place name
16. ers of each independent tool to ingest to the RI Otherwise it is impossible to keep different metadata consistent to manage the potential complexity of flows of work and to keep manual interaction at the minimum necessary for industrial application The tool aims further at providing a good practice library of software components for metadata creation that 3D tool providers can employ to integrate their tools more consistently and efficiently The tool functionality of retrieving available lists of values from the RI given specific criteria and ingesting new such values to the RI is provided as a set of java functions for all other 3D tool providers We hope that the existence of such a set of functions will help all partners to integrate their tools to the RI We also hope that the tool source code can also be used as a coding template for the ingestion mechanism that will be integrated in the 3D tools 3D 2Y2TEK 2 Workflow Considerations 2 1 Describing the output of an Event The user normally needs to specify the output of the event which is about to describe Actually workflow wise this is the first card that the user has to fill This is due to the fact that the user has to specify metadata for specific data located on his her local storage how he got these data output during which procedure event etc We believe that this is the most intuitive way to describe an event by assisting the user to answer the following questions
17. es for one file instead of many The user is also given a choice to consider all data files as one multipart object for which is prompted to define the startup data file This option is mutually exclusive to the option of generate zip for files When updating a process event all forms described below are already filled by the event details retrieved from the RI Filenames of digital objects or other files that are already ingested in the RI are denoted by a preceding the filename 18 3D 2Y2TEK n Reposit Tool Help About Output digital objects Process event Input digital objects Documentation Filename Browse 2012 08 10 proces New event Update event Load event templa _ Generate zip for files Save event template LJ Consider all output objects as multipart with startup object Ingestto RI M Project 2012 08 10 project Byzantino Pending Uploads Event processing Figure 19 Form for selecting the output of a process event For each of the displayed digital objects the user could store individual metadata information by selecting a file in the list Then a new pop up form appears see Figure 21 This edit form enables the user to add a note to the selected digital object and set or update its thumbnail image If option Generate zip for files is selected then the metadata information and thumbnail on each individual file is ignored If in update
18. fields examples 26 3D 2Y2TEK It should be noted that the displayed value in a field should be compact in order to be easily selectable thus it may vary from the detailed information presented when a new entity is introduced See section 3 5 for a presentation of the available forms for creating entities 3 6 4 Update of Events The tool also permits the editing and updating of existing Event metadata already ingested in the RI provided they comply with the Reposit Tool disciplines The user may select Update event button and a pop up will appear which allows selecting an Event from a list of Events see Figure 39 Specifically the user first choose type of event first combo and optionally a specified project second combo and finally selects from the third combo box a specified event to be updated The user can change any field of each event output input and other fields and press Ingest to RI button for activating the update process Update event Choose project l l vJ Choose event v Edit Figure 39 Form for selecting an Event for update 3 6 5 Creation of new Types To create new type values in a existing vocabulary such new acquisition types new device types etc please contact georgis ics forth gr or hrysakis ics forth gr requesting the creation of the new type 27 3D 2Y2TEK 4 Appendix 4 1 Tool properties file The tool properties files is used as configuration file
19. form for incomplete uploads incomplete files The system tries to re upload these files from their original destinations Figure 55 Message which is displayed when clicked at the status bar and no any pending uploads exist 31
20. iginal jpg v Ingestto RI Project 2012 08 10 project Byzantino Event Untitled Pending Uploads Figure 8 Form for selecting the output of an acquisition event For each of the displayed digital objects the user could optionally store individual metadata information by selecting a file in the list see Figure 8 Then a new form pops up see Figure 9 This edit form enables the user to add a note to the selected digital object and set or update its thumbnail image For process event user can select a specified type e g 2D image video etc If option Generate zip for files is selected then the metadata information and thumbnail on each individual file is ignored If in update mode the selection to be deleted form the RI is available for the user to declare that the digital object is no longer part of the specified event _ ID uuid 026d8505 8a34 4e7 e 9f0e 63cf31b71090 File mnimeio2 jpg PS Note Thumbnail Thumbnail Browse Figure 9 Form for editing output file attributes 13 3D 2Y2TEK 3 3 2 Acquisition Event By clicking at the tab Acquisition event the form describing basic information for this acquisition event appears see Figure 10 The user can insert information such as the title of the event the time and the place the event took place the responsible organization and the operators involved in the event etc r 7
21. ircean SE 14 3 3 3 ID E Pus A E E EE 16 3 3 4 DOCU E O a A mm 17 3 4 PROCESS uses esceeees 18 3 4 1 Digital OBJEC rese 18 3 4 2 f 19 3 4 3 We AB e ROO OS 20 3 4 4 DOCU ea senses E E RU IRE MEINEN UNDE UE 22 3 5 Forms for the creation and update of 65 23 3 6 Form Input fields functionality 26 3 6 1 Input field 191419 1 5 26 3 6 2 RT 26 3 6 3 Creation and update OF entities 26 3 6 4 EUBTIES sec tants M CUM HUM 27 3 6 5 AIO POF NEN TYD 27 4 APPENDIKS xp UI edid adi aUas ERNEUT 28 4 1 TOOL ces ae senate cide scenes 28 4 2 User Control Messages soiciacddhacsspsntndesmentovadenatuseued SeenacunasiedsunedoacndeaaDarunatemancusavedeassanacaiose ou dis 28 3D 2Y2TEK 3D 2Y2TEK 1 Introduction This document de
22. ity walls 107 asc M 107 bIk of 2009 05 12 capture Eastern Moat Chania city walls 107 bIk 107 jpg of 2009 05 12 capture Eastern Moat Chania city walls 107 jpg 2012 08 10 108 asc of 2009 05 12 capture Eastern Moat Chania city walls 108 asc i 108 bIk of 2009 05 12 capture Eastern Moat Chania city walls 108 bIk M M M 108 jpg of 2009 05 12 capture Eastern Moat Chania city walls 108 jpg i Selected intermediate files from process Describe earlier intermediate process v New event Update event Load event templa Save event template Inaestto RI _ No input required Project 2012 08 10 project Byzantino Pending Uploads Event 2012 08 10 Figure 22 Form for selecting the input file uuids or process output of a process event 20 3D 2Y2TEK isl Ck List selected event digital objects Figure 23 Form for selecting the output files of a previous event By pressing the Describe earlier intermediate process event button the user can enter information for the new process see Figure 24 and choose the corresponding input digital objects see Figure 25 with the same procedure as above S Reposit Tool Eventtitle 2012 08 10 process Other title process Type j 2012 08 10 proces Sofiware j l Edit New IMProcess uuid a8 Soflware Parameters Parameters file Browse XN 00000
23. le uploads of this user Synchronous ingest of files is provided as a choice through the tool properties file At the status bar there is a link labeled as Pending Uploads which on click displays all the currently pending uploads per each active session If no any pending uploads exist an appropriate message is depicted see Appendix 55 3D 2Y2TEK 3 User Interface Description The 3D Systek Reposit Tool works with the two types of events the acquisition event and process event It provides an interface based on tabbed input forms to assist the user to answer the following questions a which data were produced b by what procedure c using what input d with some documentation information asserted The purpose of the tool is to enable users to use forms instead of RDF files to interact with and be able to ingest their data in the RI These forms interact with the RI in order to assist and assure correct input in specific fields The tool can save the event descriptions in files in the local disk These files can be saved and reloaded enabling user to describe the events at his her own time After the description is completed the user can ingest the metadata collected along with the data these metadata describe to the RI 3 1 Login Form If it is the first time running the tool a login form is displayed with the following 3 fields URL the link of repository to connect User username and Password Figure 3 After filling in
24. loads Start date 2012 08 10 yyyy mm dd hh mm End date yyyy mm dd hh mm Event processing OO Figure 21 Form for editing the description and details of a process event 3 4 3 Input Digital Objects For describing the input of the process event the user can select digital objects from RI see Figure 22 By pressing Query button a pop up form appears see Figure 23 to enable the user to select as input the output files of a previous event files that were already been ingested maybe using the Reposit Tool at a previous point it time The process input except of being a set of data objects from the RI can also be the product output of another process for which the user decided that was not needed and has erased as described in section 2 3 In this case the Reposit Tool assists the user in describing the metadata for this process creating and describing a new process by pressing Describe earlier intermediate process event button These choices of input can be supported both for the same process event On the other hand if the user clicks on the checkbox No input required then the above input selections are disabled and their contents are ignored r 5 Reposit Tool Help About Output digital objects Process event Input digital objects Select digital objects from the repository Clear selected 107 asc of 2009 05 12 capture Eastern Moat Chania c
25. may be necessary to enable automatic translation and multilingual search capability of some fields The user can also create a new entity such as a new Person in the RI by New button or update an existing entity in the RI by Edit button A pop up form appears see Figure 11 for introducing the new entity or for updating the existing one for the user to provide all the details of the entity In Figure 11 is presented the form for creating updating a Person identifying first and last name of the person the organization the person is currently a member of his role in the organization a unique URI optional for identifying the Person entity if not given the system will create a UUID for this entity and a note field In section 3 5 are presented all the forms for creating new Entities The button is designed to enable the user to specify more than one values in specific input field see section 3 6 2 14 3D 2Y2TEK Last name URI Member of Til ae Role O m Note Figure 11 Form for creating a Person The Acq Location field specifies the place the Acquisition took place The form for introducing a new acquisition location provides the user the choice of specifying locations see Figure 12 as specific as a room in a building of an organization see Figure 13 or a set of coordinates see Figure 14 in the case of an outdoor acquisition In the last case a link to geonames website is p
26. mode the selection to be deleted form the RI is available via Clear button for the user to declare that the digital object is no longer part of the specified event r Digital object details ID uuid 4ac5c9e4 f791 48a2 9f62 c3d31 77e94e4 File mnimeio1 jpg Type image jpeg Note Thumbnail Thumbnail Browse Figure 20 Form for editing output file attributes 3 4 2 Process Event By clicking at the tab Process event the form describing basic information for this process event appears see Figure 21 The user can insert information such as the title of the event the time the event took place the organization and the operators actors involved in the event the software used for processing the parameters used for the processing etc Note that the tool provides more than one ways to describe the parameters by a plain text field field Software Parameters or by one or more parameter file 19 3D 2Y2TEK a Reposit Tool Help About Output digital objects Process event Input digital objects Documentation Eventtitle 2012 08 10 processing Other title processing Type 2012 08 10 proces Soflware Software Parameters Parameters file Browse iT ndis Organization M Edit New New event Operator Edit New Update event Person Days Load event templa i Save eventtemplate Inaestto RI Project 2012 08 10 project Byzantino Pending Up
27. ocumentation files for example photos video of the setup and possible documents with details on the setup installation by clicking the button Browse see Figure 18 17 3D 2Y2TEK n Reposit Tool Help About Output digital objects Acquisition event Setup amp Devices Documentation Setup Description M 2012 08 10 Documentation file s Clear Browse New event Update event Load event template J Save event template Ingest to RI Project 2012 08 10 project Byzantino i Event Untitled Pending Uploads Figure 18 Documentation tab for acquisition event 3 4 Process Event The event description of a process event is based also on a four tabbed form Output digital objects Process event and Input digital objects Documentation 3 4 1 Output Digital Object Similarly to acquisition event the user is prompted to select the output digital objects that were produced during this process event This is done by pressing the browse button see Figure 19 This button pops up a file browser for the user to select that data files from the local storage local hard disk The user is given a choice to generate a zip file using the option Generate zip for files that contains all the selected files if the data files to be ingested are going to be treated further as a set of data This also reduces the metadata information that the tool generates since it generat
28. on by a plain text filed field Setup Characteristics or by one or more configuration files The form provides a field to specify the calibration files used for this acquisition if any field Calibration file 16 3D 2Y2TEK a S Reposit Tool Help About I CC Cem Crew Software j Edit New Setup characterestics 2012 08 10 non port Setup config file Browse Calibration file Browse Mee Iv Other device j Edit New New event Update event Load event template Save event template Ingest to RI Project 2012 08 10 project Byzantino Event Untitled Pending Uploads Figure 16 Form for editing the setup and devices of an acquisition event In Figure 17 is presented the form for creating a Device entity defining details like device type serial number maker firmware notes etc This form also provides the user with a sub form for describing details on the documentation concerning the acquisition setup button Setup Documentation jj Create edit digital device Digital device ID Digital device name Type Serial number Maker Device characterestics Firmware Edit New Apply Figure 17 Form for creating a device 3 3 4 Documentation In documentation tab the user can describe in a field the setup of the whole process and include ingest related d
29. rocess events may not have input files There is also the case where a process does not have any input data The user is using software to generate data files without any data files as input The tool supports this case too by providing the user a way to declare this lack of input 2 4 Describing the documentation of an Event In some cases we need to report information about the event in the sense of attaching of documentation files e g images or text files or inserting some primitive description that summarizes the whole process This feature could be optional for both acquisition and process event 2 5 Asynchronous and synchronous ingest The default behavior of tool is the asynchronous uploading ingest of files in order to speed up the parallel ingestion of events However since large files need more time for successful uploading the Reposit Tool informs the user at the closing exiting of the application for pending files files that are currently uploading by the specified user during the current session see Appendix Figure 53 The tool suggests the user to confirm that the uploads of pending files would be stopped The user may wait until the uploading is completed At the beginning of the application the tool informs the user for incomplete files that seem to be corrupted and stopped while uploading At this case the tool informs user see Appendix Figure 54 and applies the auto re upload method that re uploads all stopped fi
30. rovided for convenience Building Exhibition space URI Building Exhibition space name Place Address Location URI Location Title Longitude x Latitude y Place Address Figure 14 Form for creating a Location by coordinates 15 3D 2Y2TEK The Acq Object field designates the physical object In Figure 15 is presented the form for specifying the object that is being digitized The user can specify whether is a museum object or an immobile object or site e g archeological site public heritage monument sculpture or building The fields in the form varies according the user selection in Figure 15 are presented the fields for specifying a museum object by its inventory number title type otherlD size relative keeper museum and note No other form of legacy data is ingested by this tool 7 Create edit physical object c5 Physical objectID Title Object name Inventory no Other ID Size Type Keeper IJ Edit New Note Figure 15 Form for identifying a Museum Object 3 3 3 Setup amp Devices By clicking at the tab Setup amp Devices the form for describing information about the hardware device data device characteristics and note used for this acquisition event appears see Figure 16 In this form the user can also specify other devices used such as lenses flashes etc The tool provides more than one ways to describe the setup configurati
31. scribes a tool for ingesting into the 3D Repository Infrastructure data objects for or from 3D Model production that have not been produced together with valid 3D Digital provenance metadata The tool guides the user during the ingest process to manually provide sufficient and consistent information which is captured in metadata Data objects in 3D Model production are typically created in individual processes which form part of an open only partially constraint workflow with complex structure In order to support the envisaged reasoning functions for data management and scientific interpretation it is critical for the consistency of the metadata that the output of one process is referred as input in the next process with exactly the same identifier as well as all persons places and other things involved in more than one process The tool however limits the possible complexity of a particular acquisition process to at most one level of sub processes The main challenge of the tool is to ensure this referential integrity by querying existing reference data in the repository and validating user input against related data in the repository The tool aims further at providing a good practice library of software components for metadata creation The tool further allows referring to and loading complete existing metadata records describing the digitized cultural object 1 1 Functional Point Characteristics The tool is based on the specifications that
32. ssage for successful ingestion The previously ingested digital objects s or zip file denoted by will be detached from this event A new zip file will be attached to it containing only the newly selected digital objects Total ingestion failed Reposit will be switched to update mode RI transaction failed Code rcerr51 Message rcerr 51 Send soap request problem caused by Metwork is unreachable connect Method createAcquisitionEvent Figure 50 Message for auto switching to update mode in case of failure as soon as the main information metadata of event has been ingested 30 3D 2Y2TEK During this session transaction s failed and did not rallbacked correctly The system will try to re apply the rollback This may take sometime Transaction s were found open or commited but not closed They may be left from incomplete ingestions Open transactions action to perform rollback and close trans cc5f2524 1f3d 44a2 b471 c8fe54d 3f d Do you want to rollback the open transactions and close all transactions File s were found pending They currently uploaded during an active session of ingestion file C Users hrysakis Documents captures iso Transferred 8 25 File s were found incomplete from previous ingestion s Auto reuploading method has been just started for files captures iso file C Users hrysakis Documents captures iso Figure 54 Message at start of application to in
33. these default values The last can be overwritten by setting different values in the properties file For example by setting LegalBodylnitEntities a all combos related with Legal Bodies should be initially loaded by Legal Bodies which label starts with a Reposit Tool Properties File urls http 139 91 183 45 8080 SYSTEK services RIWS wsdl deletefiles no querylog yes sync no optional initialization for combos java regular expressions PersonlInitEntities abcd LegalBodyInitEntities abcd LocationlInitEntities abcd PhysicalObjectInitEntities abcd DigitalDeviceInitEntities abcd SoftwarelnitEntities abcd EventInitEntities 20 PhysicalObjectTypes a VocabularyTypeltems 3 4 2 User Control Messages We present a list of basic messages that are displaying due to control operations of Reposit Tool s user 28 3D 2Y2TEK Connection error ERROR rcerr 51 Send soap request problem caused by Metwork is unreachable connect Please close all forms save event data and retry when connection is back on Use the next button to edit multiple values OK Figure 43 Message for editing multiple values Figure 44 Message for wrong date format The selected value Her for Location is not correct Please re select a value from the drop down list Figure 45 Message to re select a value from a specified combo box 29 3D 2Y2TEK Figure 48 Me
34. tton Load event template the user may choose to load an existing event description from the local storage local hard disk After he she has finished with the editing of an event he she may save the event descriptions for re evaluation in a file on the local disk by pressing Save event template or ingest the event along with its data in the RI by pressing Ingest to RI Event Descriptions used as templates All saved event description files once ingested can no longer be used for re ingestion of the same data Instead they may be used as event templates they can be reloaded and used without having the user to re enter the same information for a set of events with the same details e g same organization actors same S W and S W parameters etc only having omitted all input output information The left scrollbar displays the events that are currently described during one event description Specifically during the editing of a process event the user may desire to describe more than one process events as described in section 2 3 2 this left scrollbar enables the user to jump from the one process event to the other 3 3 Acquisition event The event description of an acquisition event is based on a four tabbed form Output digital objects Acquisition event Setup amp Devices and Documentation 3 3 1 Output Digital Object For describing the acquisition event the user is prompted to select the output digital objects that
35. were produced during this acquisition This is done by pressing the browse button see Figure 8 This 12 3D 2Y2TEK button pops up a file browser for the user to select that data files from the local storage local hard disk The user is given a choice to generate a zip file using the option Generate zip for files that contains all the selected files if the data files to be ingested are going to be treated further as a set of data This also reduces the metadata information that the tool generates since it generates for one metadata file instead of many The user is also given a choice to consider all data files as one multipart object for which is prompted to define the startup data file This option is mutually exclusive to the option of generate zip for files see Figure 8 When updating an acquisition event all forms described below are already filled by the event details retrieved from the RI Filenames of digital objects or other files that are already ingested in the RI are denoted by a preceding the filename Help About Output digital objects Acquisition event Setup amp Devices Documentation Filename Clear Browse mnimeio1 jpg mnimeio2 jpg mnimeio original jpg 2012 08 10 non port 4X 7 gt vx New event Update event Load event template enerate zip for files V Consider all output objects as multipart with startup object Save event template mnimeio or
Download Pdf Manuals
Related Search