http://smartech.gatech.edu/handle/1853/28534 Search the Channel search http://smartech.gatech.edu/simple-search http://smartech.gatech.edu/handle/1853/28538 Title: 4th International Conference on Open Repositories Program <br/> <br/>Description: 4th International Conference on Open Repositories Tue, 28 Apr 2009 22:58:59 GMT http://smartech.gatech.edu/handle/1853/28532 Title: FESL: Fedora Enhanced Security Layer (A Community-Based Project) <br/> <br/>Authors: Shin, Eddie <br/> <br/>Abstract: While there have been many significant changes to Fedora since the release of Fedora 3.0, there has not been any new work in the area of authentication and authorization. At the same time, there have been many requests from the Fedora user community to support a wider range of authentication methods and to better enable management and enforcement of XACML authorization policies. As a result, members of the Fedora community initiated the FESL project to re-factor and improve the Fedora security architecture. The FESL team has decided to incorporate Muradora's authentication and authorization modules into Fedora. The FESL project team will re-factor the current security implementation of the core Fedora service into a more modular architecture based on Java Authentication and Authorization Service (JAAS). In terms of making XACML easier to use, the FESL team will work towards providing a uniform "vocabulary" for typical authorization use cases. This vocabulary will make XACML policies more easy understood by end users without specific knowledge of Fedora's APIs or the XACML standard. A uniform vocabulary will also aid in the development of a more intuitive UI editor for expressing authorization requirements. <br/> <br/>Description: 4th International Conference on Open Repositories; This presentation was part of the session : Fedora User Group Presentations; Date: 2009-05-20 03:30 PM – 05:00 PM Tue, 19 May 2009 22:58:59 GMT http://smartech.gatech.edu/handle/1853/28531 Title: Enhanced Content Models for Fedora <br/> <br/>Authors: Blekinge-Rasmussen, Asger <br/> <br/>Abstract: This presentation introduces Enhanced Content Models for Fedora. Enhanced Content Models have a number of new features compared to the Fedora 3.0 content models. First of these is the more elaborate specification of the data objects. Second is the repository view system, which allows the repository to dynamically remap the contained data to virtual data objects. And third is the object creation templates, which allows the content models to behave as object classes from which new data object instances can be made. All our work is under the Apache 2.0 License, and will be available as add-ons to Fedora. Fedora is an extensible repository system, containing data objects and content models, which hold descriptions of the data objects that subscribe to them. In Fedora 3.0 Content Models express the classes of objects, and tie data objects to disseminators, but do little else. Content Models are formal descriptions of data objects, which should be distinguished from datamodels, which are descriptions of collections of data. Having a datamodel is a requirement for many digital repositories and the easiest solution is creating an interface that only allows data to be entered in a special format. If all data is input through this interface, it will adhere to the datamodel. Unfortunately, this has the side effect of coupling the datamodel to the program code of the interface. We believe that the datamodel should not be part of the interface, it should be part of the repository. We achieved this by enhancing the Content Models. The Enhanced Content Models can specify the cardinality and target classes of relations, and schemas for datastreams. We have implemented a validator, which checks data objects against their Content Models. A set of Enhanced Content Models makes up a datamodel. In Fedora, you might have atomic objects making up a "record", but for indexing purposes, this record must be flattened to one compound. Enhanced Content Models can specify how to do this flattening, in the repository view system, and we have implemented a webservice to create such compounds. In many OO programming languages new objects are created as instances of a class. Enhanced Content Models implements this pattern. You can declare certain data objects to be templates for an enhanced content model. We have developed a webservice that can create new objects in Fedora, given a content model and a template to use as basis. <br/> <br/>Description: 4th International Conference on Open Repositories; This presentation was part of the session : Fedora User Group Presentations; Date: 2009-05-21 08:30 AM – 10:00 AM Wed, 20 May 2009 22:58:59 GMT http://smartech.gatech.edu/handle/1853/28530 Title: PhotoCat: Implementing a Cataloging Tool for a Live Fedora Repository <br/> <br/>Authors: Ozakca, Muzaffer; Dunn, Jon W. <br/> <br/>Abstract: In this presentation, we will discuss the development process of a metadata cataloging application called PhotoCat (short for Photo Cataloging Application) created by the Indiana University Digital Library Program to allow catalogers and archivists to easily enter and manage item-level MODS descriptive metadata for image collections in IU's Fedora repository. Although admittedly this is not a unique use of Fedora, we faced a few interesting challenges along the way in using Fedora as a storage backend for such a tool. PhotoCat provides access to metadata records for multiple collections in a flexible way. Even though they may all use the same metadata standard (e.g. MODS), each collection may use different subsets of the available elements or use elements in slightly different ways. PhotoCat, in addition to search, browse and user management capabilities, provides a customizable interface and metadata model that define a) the Web form that accepts user input and b) instructions for populating a metadata record from that form. Functionality similar to this is found both in Fez and Muradora, two popular Fedora front-ends. In this presentation, we will talk about how our implementation is different from these systems and the unique requirements that led to our current implementation. One of the challenges we ran into was related to batch updates. Users familiar with traditional online database applications expect updates to multiple records to be reflected nearly instantaneously. Updating a single element in a batch of XML metadata datastreams in Fedora, on the other hand, requires that each object's datastream be retrieved, updated, and stored back in the repository. One of the options for achieving a perceived real time operation was limiting updates to a small fixed number of records, but this wasn't acceptable for large collections with thousands of records that needed to be updated at the same time. We also considered placing a faster middleware layer between the application and Fedora, but ended up opting for an asynchronous, behind the scenes approach for this issue. Another big challenge was generating metadata records that are syntactically and semantically correct. One of the aims of the project was that the metadata generated by the application would obey established guidelines and best practices for a given metadata standard. We considered XForms for this purpose but ended up implementing our own display/model web component, and in this presentation, we will discuss the reasons for that choice. <br/> <br/>Description: 4th International Conference on Open Repositories; This presentation was part of the session : Fedora User Group Presentations; Date: 2009-05-21 08:30 AM – 10:00 AM Wed, 20 May 2009 22:58:59 GMT