Event-Based Model for Reconciling Digital Entities Ahmet Fatih Mustacoglu Ahmet E. Topcu Aurel Cami Geoffrey C. Fox Indiana University Computer Science Department Community Grids Laboratory May 23, 2007 CTS-2007, Orlando, FL, U.S.A. 3/6/20161

Outline  Introduction Annotation Tools and Collaboration  Motivation  Prototype Semantic Research Grid (SRG) System  SRG Key Concepts  Research Issues  SRG System Modules Overview  Example Applications  Conclusion 3/6/20162

Annotation Tools and Collaboration  Rapid development of tools and services aimed at fostering online collaboration and sharing between users and communities: Social Bookmarking Tools supports annotation using keywords called tags and sharing  e.g. del.icio.us Tools for annotation and sharing of scholarly publications  Connotea  Citeulike  Bibsonomy Social Networking Tools(MySpace) Video Sharing and annotation  e.g. YouTube 3/6/20163

Typical User Library in Connotea 43/6/2016

Motivation  Numerous annotation tools  Generates multiple instances of metadata about the same object  Huge amount of data  Necessity for the reconciliation  Requirement for reconciliation  Lack of interoperability between annotation sites  Applying service-based architecture to annotation systems 3/6/20165

Big Picture: Semantic Research Grid (SRG) Architecture 3/6/2016 6

Key Concepts of System Architecture  Digital Entity (DE): a digital collection of metadata for a citation  Event: a time-stamped action on a digital entity. Our event-based model consists of: Major Events:  Insertion or deletion of a digital entity Minor Events:  Modifications to an existing digital entity Dataset:  Collection of minor events  Service-based Framework (SOAP over Http) 3/6/2016 7

Research Issues  Event-based model Manipulating data and metadata How to build event-based model ?  Major and Minor events  Datasets (collection of minor events) How to apply event-based model ? How to apply modifications to a record (Digital Entity) ?  Keep them in user’s session and let user apply them  Apply them directly to a DE How to merge metadata field of a Digital Entity ?  Identification of metadata fields as dynamic or static field  How to apply service-based framework as wrapper? 3/6/2016Ahmet Fatih Mustacoglu8

SRG System Modules I  Digital Entity (DE) Management Service Manual DE entity into the system DE history DE versioning and flexible choices (rollback) Editing and more info tools for a DE (Update Model)  Session and Event Management Services Event and dataset management DE view options User credentials (username/password) - cookie-based  Annotation Tools Service Transfer Service Download service Upload Service 3/6/20169

SRG System Modules II  Search Tools Services Google Scholar/Windows Live Academic Google Scholar Advanced Local Database Search:  Via integrated PubsOnline Tool from Indiana University  My Research Database  My Research Database Advanced  Authentication and Authorization Services Login and Logout service DE Access rights management Database access rights management Administrative tools  Other Services User Registration Username and password recovery User’s Profile Management DE metadata view options 3/6/201610

Example Applications  Transfer  Download/Upload  Modify Digital Entity (DE)  Share DE with other users  More info of a DE  History of a DE and rollback 3/6/ CiteULikeDelicousConnotea Research Database Research Database Research Database Core Web Services

Typical Scenario for Generating Minor Events  1: Client tries to modify a DE  2: Check user access rights.  3-4: If user has write access to this DE; (a) build the current DE metadata from its events, (b) saved the update metadata into session as minor event.  5: Show confirmation message 3/6/ Client SRG Web Services 1,52 Session and Event Management 4 Main Database RDBMS Research Databases 3

Typical Scenario for Updating a DE from Minor Events via Dataset Creation 1: Client can access all minor events for each DE from the user session 2-3: Select minor events to create dataset(s), and apply them on top of latest DE. Confirm dataset(s). 4: Save the events into the associated research database 5: Confirmation message 3/6/ Client Session and Event Management SRG Web Services RDBMS Research Databases Main Database 3

Typical Scenario for Downloading DEs  1 : Client request to download records from a social bookmarking website into a research database  2: Check user access rights  3-4-5: If user has write access, and DEs do not exist, then download them into the associated research database. If a DE exist in the research database, save the update metadata into user session as a minor event  6: Confirmation message 3/6/ Client RDBMS Research Databases SRG Web Services Main Database Session and Event Management Social Bookmarking Websites 3

Summary  This paper addresses the following open research issues in management of Digital Entities: Architecture for reconciling digital entities Allows the manipulation of a digital entity Applies Event-based model based on the concept of:  Major events  Minor events  Datasets Provides a rollback feature to:  Support for history tool for a DE  Merge and change the content of a digital entity A service-based framework for using existing annotation tools through web services  Prototype project web site: 3/6/

THANK YOU! Ahmet Fatih Mustacoglu 3/6/201616