A lightning talk at Samvera Virtual Connect 2016. The talk was in two parts with the second given by Matthew Phillips of Durham University. Unfortunately, his slide deck is missing from the archive.
Keyword:
Research data management, Hydra, Virtual Connect 2016, and Lightning talk
Subject:
Hydra Project
Creator:
Allinson, Julie
Contributor:
University of York, Phillips, Matthew, and Durham University
How to Write Module-Based JavaScript with RequireJS and the AMD (Asynchronous Module Definition) PatternTired of worrying about load order for your script includes? Tired of polluting the global namespace? Want to write more re-usable JavaScript code with discrete modules? Maybe RequireJS / the AMD pattern is right for you! This presentation will go through the construction of a simple RequireJS-based JavaScript app with a few modules. and A workshop given at Samvera Connect 2017 described thus
A presentation given at Connect 2017 described thus and Presentation on a gem for Hyrax models and authorities, which provides a central place for creating models for different types of works. Each new model draws on a central pot of properties to declare the set of properties needed to fully describe the particular work. The gem already exists and has sample models for journal article, thesis and more. In this presentation we will work through the process of defining a new model and then using that model in a Hyrax application. The idea behind the gem is to make it easier for developers to deploy new models, and provide a place for metadata folks to jointly define re-usable models.
Keyword:
Hyrax, Connect 2017, and Samvera
Subject:
Samvera Community
Creator:
Hardesty, Juliet L and Allinson, Julie
Contributor:
CoSector, University of London and Indiana University
A presentation given at Connect 2017 described thus and In this presentation, we present Fedora 4’s performance in different use cases. These use cases are the most general use cases that were developed by the Fedora 4 performance team. We compare the performance between different versions of Fedora 4 and demonstrate the improvement between these versions. We will also describe the procedures of these performance experiments and demonstrate the software we use (Ansible, AWS, and JMeter). Our performance experiments are conducted in the AWS ecosystem, and we use an R graph tool to visualize the JMeter result. With the AWS grant, we can do many different performance experiments in many scales. Moreover, it is easy to repeat and verify the performance results using AWS. The Fedora 4 performance team wants to know more about the Samvera community’s interests related to the Fedora 4 performance. We plan to gather more use cases from the Samvera community, including middleware such as Solr, Camel, and Fuseki, etc. We can investigate, explore issues, and continue enhancing the future of Fedora 4.