Databases evolution in CulturePlex Lab
Upcoming SlideShare
Loading in...5
×
 

Databases evolution in CulturePlex Lab

on

  • 1,067 views

The evolution of needs and requirements and its impact on the databases usage in the CulturePlex Lab.

The evolution of needs and requirements and its impact on the databases usage in the CulturePlex Lab.

Statistics

Views

Total Views
1,067
Views on SlideShare
962
Embed Views
105

Actions

Likes
0
Downloads
7
Comments
0

1 Embed 105

http://versae.blogs.cultureplex.ca 105

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Databases evolution in CulturePlex Lab Databases evolution in CulturePlex Lab Presentation Transcript

    • Presentation of Databases Evolution in the CulturePlex Laboratory De la Rosa, J; Muñoz, D; Suárez, JL {jdelaros, dmunozes, jsuarez} at uwo dot ca 2010
    • BaroqueArt ( http://baroqueart.cultureplex.ca ) SQL based
    • Traditional SQL
      • Databases with more than 100K objects and relationships.
      • Complex data scheme.
      • Humanists should do queries with no SQL knowledge.
      Need a tool to assist for making complex queries. django-qbe http://versae.github.com/qbe
    • django-qbe ( http://versae.github.com/qbe )
      • View and autodiscover relations among the models in a visual way.
      • Tabular creation of queries with fields to show, criterias, lookups and order (only AND conditions by now).
      • Auto adition of right fields when ForeignKey or ManyToMany fields are selected.
      • Bookmarklet to save and share the queries.
      • Export results to .csv, .odt and .xls, but it's extensible by the user.
    • django-qbe ( http://versae.github.com/qbe )
    • Traditional SQL
      • Old data schemes, sometimes from 4 years ago.
      • Numerous changes in the main scheme.
      • Almost one big migration per year of all data.
      • Humanists need enrich the data continuously.
      Need a tool to semantic annotation via ontologies. django-descriptors https://github.com/versae/descriptors
    • django-descriptors ( http://github.com/versae/descriptors )
      • Descriptors classified in a tree: ontology.
      • Main ontology can be modified and enriched by the users.
      • Users and user groups can share their own (sub)ontologies.
      • Any object can be “described” with any number of descriptors.
      • Descriptions can have a value associated.
    • django-descriptors ( http://github.com/versae/descriptors )
    • Traditional SQL
      • Hard to add new tables.
      • Hard to create new properties.
      • Very slow queries with several JOINs.
      • Humanists need a lazy and dinamic definition of schemes.
      Need a tool to create free relations and properties Sylva https://github.com/escalant3/graphgamel
    • Sylva ( http://github.com/escalant3/graphgamel )
      • No tables, only objects and relations (a NoSQL GraphDB).
      • Any number of attributes on objects and relations.
      • Lazy and dynamic schemes to check integrity.
      • Support to media content (images, audios and videos).
      • Facilities to manage users, groups and permissions.
      • Easy to imeplement ontologies and semantic descriptions.
      • Traverses to query the underlying graph.
      • Analysis and visualization of huge data sets.
    • Sylva ( http://github.com/escalant3/graphgamel )
    • Sylva ( http://github.com/escalant3/graphgamel )
    • Questions? Thank you