1 / 23

Integrated Collaborative Information Systems

Integrated Collaborative Information Systems. Ahmet E. Topcu atopcu@cs.indiana.edu Advisor: Prof Dr. Geoffrey Fox. Outline. Introduction Motivation Research Issues Architecture Measurements and Analysis Conclusions Contributions. Introduction.

carolcompton
Download Presentation

Integrated Collaborative Information Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integrated Collaborative Information Systems Ahmet E. Topcuatopcu@cs.indiana.edu Advisor: Prof Dr. Geoffrey Fox

  2. Outline • Introduction • Motivation • Research Issues • Architecture • Measurements and Analysis • Conclusions • Contributions

  3. Introduction • Efforts for collaboration and sharing between users and communities. • Grid • Virtual Organizations • Sakai • Collaboration and Learning Environment for Education • Web 2.0 • Represents new web-based services. • Provides rich and lightweight online tools • Provides reusable services and data • Updates software and data often very rapidly • Provides interactive user interfaces • Provides an architecture for easy user contribution

  4. Web 2.0 Examples • Blogs (blogger.com, GoogleBlog) • Wikis(Wikipedia, WikiWikiWeb) • Social Networking Tools(MySpace ,LinkedIn) • Social Bookmarking Tools(del.icio.us ,YouTube) • Domain of scientific research (CiteULike , Connotea , and Bibsonomy) • Domain specific academic search tools(CiteSeer, Google Scholar, Windows Live Academic)

  5. Motivation • Numerous annotation and search tools. Each of them has different capability and not completed defined metadata • Need for exploiting large set of data sources from various tools • Integration of major annotation and search tools in order to use them having additional functionalities for scientific research • Utilize the best capabilities of the tools

  6. Motivation II • Necessities for integration • Need for common data format • No easy way to find all publications • Example: A search in Google Scholar for the publications of our research lab (Community Grids Lab) will return only about 20% of the total CGL publications. • Wealth of information contained in numerous field remains largely outside the scope of tools • What happens if tool you choose is not adopted or worse just disappears

  7. Research Issues • Integration • Building a model to • integrate community tools and adding value to existing systems • natural collection of related documents easily • support more metadata • support tagging • Scalability • Investigate system behavior for increased message rate per second • Flexibility and Extensibility • Easy to add and remove service mechanism • Easy of integrating annotation and search tools

  8. Architecture Principles • Community-centric platform of services • Integration of dynamic publication, search tools into Cyberinfrastructure based scholarly research. • Integration such scientific research defining metadata and using various URL, and map them. • Services that aggregate information from a variety of sources (i.e., “mash-up” tools) and provide added value to communities of researchers • Do not build a new tagging and search systems. Reuse the tools and adding value to them • Easier to link together all relating information common Digital Entity (DE)

  9. Integrated Collaborative Information Systems (ICIS) Architecture

  10. Integrated Collaborative Information Systems (ICIS) Architecture Components • Tools external web tools to provide services to clients • Integration Manager have information service and provide communication between tools, client, and responsible for integration operation in the system • Filter operates two-way data filtering • Permission Handler checks existing Digital Entity (DE)s permission or build a new permission token for new DEs • Data Manager provides a mechanism to extract data from a repository and insert data into a repository • Storage maintains user data and permissions in the database.

  11. Summary: Architecture • Build integration architecture • We do not reinvent existing tools • Use existing features of tools • Supports tagging services • Provides common metadata • Allows to use consistent data • Provides common resolution of filters • Supports authorization of users

  12. Use Case: Collection of Metadata from web pages • Collect • Digital Entities in web pages using HTTP methods. • Analyze • Using heuristic methodology to extract metadata fields of the Digital Entities for publications • Build • RSS objects using collected Digital Entities. • New tags using collected Digital Entities. • Compare • Collected Digital Entities from web pages with the existing Digital Entities in ICIS repository. • If they are: • different: Store new Digital Entities in ICIS repository. • same:Option to update tags and other fields. • Share • New Digital Entities with other tools using ICIS repository.

  13. Security Model • Security in web 2.0 can be limited. • We implemented a simple but more powerful security model around local tools that wrap Web 2.0 systems. • We used an access-control matrix model to provide security for our information system • Supports multiple groups and multiple users for each Digital Entity (DE). • Similar to UNIX file system • The Unix RWX bits corresponds to Read, Write, and Execute operation for each file and directory. • In our system, DE correspond to the file element and folder corresponds to the directory element. • For each DE and folder, there are three types of access rights defined in the systems: Read, Write, and Delete.

  14. Security Model II • We have a security model that supports • Level of Authorization • Roles are defined as Super Administrator (SA) and Group Administrator (GA), User (U) • The system allows having more than one SA. • An existing SA can add other SAs to the system. • SA can assign any U to become GA, and remove GA from group. • Each group should at least one GA. GA add/remove U from group • U can allow other U and groups to share their resources • User profile • Share user profile between sites.

  15. Benchmarks and Environments • Message rate scalability investigation • Search operation • Using Database Access • Using Memory Utilization • Test environments • Apache Axis version 1.2 • Apache Tomcat Server version 5.0.28 • Java 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) • The maximum heap size of Java Virtual Machine(JVM) is 1024 MB

  16. Integrated Collaboration Information System(ICIS) Framework • Search local repository using database access with increasing Message rate

  17. Message rate scalability result (Search using Database)

  18. Integrated Collaboration Information System(ICIS) Framework II • Search local repository using memory with increasing Message rate

  19. Message rate scalability result (Search using Memory Utilization)

  20. Contribution • System Research • Providing architecture and model for integration of collaborative systems • Integration and interoperability of annotation, search tools, and web search tools • Collaboration of the users sharing resources. • Increasing performance and scalability using memory utilization • Providing flexibility allowing integration of different tools having common metadata. • Easy to add and extend service mechanism • Supports authorization and event based mechanism • System Software • An ICIS Infrastructure of Internet Documentation and Integration of Metadata (IDIOM) systems

  21. Thanks! Questions?

More Related