Hydra as a Digital Asset Management System

We are currently looking for a solution to store the different forms of digital objects/assets that are generated by various researchers/academics/departments/faculties at Lancaster University. The traditional repository model does not feel like it is best suited to accommodate the ever expanding range of digital assets. We are talking about Research Data, Digitised objects, Open Educational Resources, Video and Audio files, Software packages, etc. So we started looking into other appropriate solutions. From my previous experience, I remember Fedora was designed for this very purpose. The hint is in the name, Flexible Extensible Digital Object Repository Architecture. We are really keen on the flexible and extensible aspects. However, experience has also taught me that Fedora can become very complex to manage very quickly. Something, we at Lancaster, can’t afford at this time with our limited resources. At the same time, we are also looking into two wrappers/solutions on top of Fedora, aptly named as Hydra and Islandora. Hydra is based on Rails (Ruby) whereas Islandora is based on Drupal (Php). Considering we have expertise in neither (we are primarily a Django/Python shop), we are open to both solutions, or something else completely. Between Hydra and Islandora, however, it seems like Hydra

Continue Reading

Sencha Touch 2.3, hasMany association, and duplication of store entries

If you are working with Sencha Touch 2.3 (ST from this point onwards), then you may have developed a love/hate relationship with the platform like myself. Some aspects of the framework are great, whereas some others are sadly atrocious. The lack of coherent document, and the wide variety of conflicting information also does not help. In a recent incident, I am using a hasMany association in the model and found a peculiar issue happening. To give you background of the issue, I have a model called Session which has a hasMany relationship with another model called Participant. Both models below: The Session model: Ext.define('MyApp.model.Session', { extend: 'Ext.data.Model', requires: ['MyApp.model.Participant'], config: { idProperty: 'id', fields: [ { name: 'id', type: 'int' }, { name: 'number', type: 'string' }, { name: 'time', type: 'string' }, { name: 'date', type: 'string' }, { name: 'day', type: 'string' }, { name: 'title', type: 'string' }, { name: 'abstract', type: 'string' }, { name: 'track', type: 'string' }, { name: 'room', type: 'string' }, { name: 'building', type: 'string' } ], hasMany: { model: 'MyApp.model.Participant', name: 'participants', primaryKey: 'id', foreignKey: 'session_id', associationKey: 'participants' } } }); The Participant model: Ext.define('MyApp.model.Participant', { extend: 'Ext.data.Model', config: {

Continue Reading

Site Footer

Sliding Sidebar

Blog of Masud Khokhar

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Currently Reading