This document discusses Omeka, an open source digital publishing platform. It can be used to create digital exhibits and collections, host entire websites, and add features like mapping and QR codes through plugins. The presentation describes how Drexel University Archives customized an Omeka site and used it for student history projects. Examples of student exhibits are provided. Considerations for implementing Omeka for student projects are outlined, and alternatives like blogs and ContentDM are mentioned for other digital needs beyond exhibits.
The document discusses exploring the use of Omeka software as a learning object repository for LOR. It provides an overview of Omeka, including that it is open source and can be hosted on their servers. It outlines user roles in Omeka and highlights of its functionalities, including uploading, describing, and searching learning objects. File formats that could be supported are listed. Plugins that may be useful are identified. A demo of Omeka is planned to discuss organization, customizing the upload form, file limits and other topics.
This document provides an overview of Omeka, an open-source digital collection management system. It discusses what Omeka is, its advantages for cultural heritage institutions, how to set up an Omeka site, important considerations for digital collections like copyright and metadata, and examples of plugins that can extend its functionality. The goal is to help attendees understand how Omeka can be useful for their institution to publish and exhibit digital collections online.
This document provides an overview of the open source content management system Drupal. It describes Drupal as a flexible CMS built on PHP and modular architecture. Core features include nodes, taxonomy, views, and themes. Key terms are defined such as modules, blocks, and users/roles. The document outlines some top Drupal modules, advantages of Drupal for libraries, potential obstacles, and resources for learning more.
Ebooks without Vendors: Using Open Source Software to Create and Share Meanin...Matt Weaver
When you start building your own ebook collections from items in your community, you stop looking at them as licensed products and start seeing them as tools. In this talk I present the open source tools used to create The Community Cookbook website I created when I worked at Westlake Porter Public Library:
http://cooking.westlakelibrary.org
This presentation has been updated since the previous version.
I wrote about this project for codelib. The article includes more technical details: http://journal.code4lib.org/articles/9911
Ebooks without Vendors: Using Open Source Software to Create and Share Meanin...Matt Weaver
When you start building your own ebook collections from items in your community, you stop looking at them as licensed products and start seeing them as tools. This talk I present the open source tools used to create The Community Cookbook website I created at Westlake Porter Public Library:
http://cooking.westlakelibrary.org
Presented at the Indiana Online Users Group Spring Meeting, May 16, 2014 in Indianapolis, IN. Slides updated for Oct. 10, 2014 talk at Ohio Library Council's Convention & Expo.
UPDATE: I wrote about this project for codelib. The article includes more technical details: http://journal.code4lib.org/articles/9911
This document discusses various tools and add-ons available for building academic websites in Plone. It covers features like theming, custom content types, subsites, fundraising integration, calendaring, laboratory information management, online exhibits, and two venerable add-ons - Faculty/Staff Directory and CMF Bibliography AT. The Faculty/Staff Directory allows creating personnel directories tailored for educational institutions. CMF Bibliography AT provides tools for creating and managing bibliographic references. Both add-ons are widely used but also have limitations that newer alternatives may address.
Museums, libraries, art institutes, and many other types of organizations need online exhibits - websites that mimic the experience of walking through a gallery discovering interesting and beautiful objects. Dumbarton Oaks Research Library and Collection recently completed a major website redesign, with Plone as their chosen CMS, and online exhibits are an important part of the new site. They wanted many features, but they also wanted online exhibits to be easy for content editors - even interns - to create.
In this talk Sally Kleinfeldt and Alec Mitchell describe collective.exhibit the new open source Plone add-on for online exhibits that we have created for Dumbarton Oaks and for the Plone community. Sally will provide background about what Dumbarton Oaks wanted in their online exhibits. Alec will describe our implementation, covering our use of Dexterity content types, bulk content creation, and how we used templates to provide a rich feature set while still making it easy for inexperienced content editors to create exhibits.
The document discusses exploring the use of Omeka software as a learning object repository for LOR. It provides an overview of Omeka, including that it is open source and can be hosted on their servers. It outlines user roles in Omeka and highlights of its functionalities, including uploading, describing, and searching learning objects. File formats that could be supported are listed. Plugins that may be useful are identified. A demo of Omeka is planned to discuss organization, customizing the upload form, file limits and other topics.
This document provides an overview of Omeka, an open-source digital collection management system. It discusses what Omeka is, its advantages for cultural heritage institutions, how to set up an Omeka site, important considerations for digital collections like copyright and metadata, and examples of plugins that can extend its functionality. The goal is to help attendees understand how Omeka can be useful for their institution to publish and exhibit digital collections online.
This document provides an overview of the open source content management system Drupal. It describes Drupal as a flexible CMS built on PHP and modular architecture. Core features include nodes, taxonomy, views, and themes. Key terms are defined such as modules, blocks, and users/roles. The document outlines some top Drupal modules, advantages of Drupal for libraries, potential obstacles, and resources for learning more.
Ebooks without Vendors: Using Open Source Software to Create and Share Meanin...Matt Weaver
When you start building your own ebook collections from items in your community, you stop looking at them as licensed products and start seeing them as tools. In this talk I present the open source tools used to create The Community Cookbook website I created when I worked at Westlake Porter Public Library:
http://cooking.westlakelibrary.org
This presentation has been updated since the previous version.
I wrote about this project for codelib. The article includes more technical details: http://journal.code4lib.org/articles/9911
Ebooks without Vendors: Using Open Source Software to Create and Share Meanin...Matt Weaver
When you start building your own ebook collections from items in your community, you stop looking at them as licensed products and start seeing them as tools. This talk I present the open source tools used to create The Community Cookbook website I created at Westlake Porter Public Library:
http://cooking.westlakelibrary.org
Presented at the Indiana Online Users Group Spring Meeting, May 16, 2014 in Indianapolis, IN. Slides updated for Oct. 10, 2014 talk at Ohio Library Council's Convention & Expo.
UPDATE: I wrote about this project for codelib. The article includes more technical details: http://journal.code4lib.org/articles/9911
This document discusses various tools and add-ons available for building academic websites in Plone. It covers features like theming, custom content types, subsites, fundraising integration, calendaring, laboratory information management, online exhibits, and two venerable add-ons - Faculty/Staff Directory and CMF Bibliography AT. The Faculty/Staff Directory allows creating personnel directories tailored for educational institutions. CMF Bibliography AT provides tools for creating and managing bibliographic references. Both add-ons are widely used but also have limitations that newer alternatives may address.
Museums, libraries, art institutes, and many other types of organizations need online exhibits - websites that mimic the experience of walking through a gallery discovering interesting and beautiful objects. Dumbarton Oaks Research Library and Collection recently completed a major website redesign, with Plone as their chosen CMS, and online exhibits are an important part of the new site. They wanted many features, but they also wanted online exhibits to be easy for content editors - even interns - to create.
In this talk Sally Kleinfeldt and Alec Mitchell describe collective.exhibit the new open source Plone add-on for online exhibits that we have created for Dumbarton Oaks and for the Plone community. Sally will provide background about what Dumbarton Oaks wanted in their online exhibits. Alec will describe our implementation, covering our use of Dexterity content types, bulk content creation, and how we used templates to provide a rich feature set while still making it easy for inexperienced content editors to create exhibits.
Museums, libraries, art institutes, and many other types of organizations need online exhibits - websites that mimic the experience of walking through a gallery discovering interesting and beautiful objects. Commercial museum collections management systems often provide this, but they are expensive and their features are often limited or require extensive customization. Open source exhibit software has proliferated in recent years, and some of these systems now provide features that approach CMS functionality. But what if you are starting with Plone, which is already a full-featured CMS?
Dumbarton Oaks Research Library and Collection is engaged in a major website redesign, and they have selected Plone as their CMS. Online exhibits will be an important part of their new website. They envisioned many features, such as image panning and zooming, timelines, favorites, and object comparison, and they also envisioned that online exhibits would be easy for content editors - even interns - to assemble. In this talk I will describe the online exhibit package that we have created for Dumbarton Oaks, and our incremental approach to defining and implementing it.
Drupal is from Mars, Wordpress is from Venus: Finding your library's CMS soul...sbclapp
Drupal and WordPress are the two most popular open-source content management systems. The document provides an overview and comparison of Drupal and WordPress, discussing their features including ease of use, community support, extensibility, custom content types, user roles, and more. Key differences are that Drupal typically requires more technical skills but allows for more complex, large-scale sites, while WordPress is very easy to use for small to medium sites through plugins and themes. The document aims to help libraries choose which system better fits their needs and capabilities.
Creating Dynamic Landing Pages for Drupal with Panels - WebinarSuzanne Dergacheva
Have you ever wanted to create a stand-alone campaign page on your website? Or prototype a new homepage layout just to see how it would look? The Panels module gives us the tools to build all kinds of landing pages in Drupal. Panels also has lots of other functionality, allowing you to create layouts and take control of how content is organized and displayed. All this, without having to write custom code.
In this webinar, we'll walk through some of the top use cases for Panels. We'll also talk about some best practices and things to avoid to make sure that you're using Panels effectively on your website.
- See more at: http://evolvingweb.ca/training/creating-dynamic-landing-pages-drupal-panels
This document introduces Drupal, an open source content management framework. It discusses Drupal's history and community, how it can be used to build and manage websites, and how its modular architecture allows for extensibility. Key points include that Drupal was founded in 2001, powers around 2% of websites, and has a large global community. Its core handles common site functions while thousands of contributed modules add additional features.
Drupal architectures for flexible content - Drupalcon Barcelonahernanibf
We got to the point where the old Drupal mantra of creating content first to see it later is not enough to suceed with content editors. Drupal is competing and replacing other CMS and platforms where the lack of flexibility is the problem #1 for content editors. They are expecting full flexibity on how content is created, displayed, approved and published. However this introduce a common problem for web developers and site builders: how can you provide this full flexibility without having to be constantly on the hook for further development or configuration.
Modules like panels and panelizer, projects like Spark and distributions like panopoly and demo framework helped change the panorama in Drupal and the expectations that are set when sites are built.
In this session we will look to a set of common problems and real examples when creating content and layout for pages with demanding editorial teams. We will look and evaluate common options and recipes.
How can complex content and rich pages be structured ? Free HTML format in different fields? Structured data in complex fields? Use paragraphs or field collection? Different content items in different items/entities? How to glue it all together?
How can indivual page layout be managed providing flexibility but also control? Rely on templating system and view modes? Use contrib modules like panels and panelizer or display suite? Mix several approaches and modules?
How can I add any content to any page and choose its display ? How can I have a list of curated widgets ready to use by the content team to deploy anywhere or in any section?
How can pages and sections be managed before approved and published? Use preview systems and inline editors? Use workbench or workflow for layout? Rely on more complex content staging systems? Use separated environments?
These are daily problems that architects and developers face in every project. As a technical architect in Acquia it is uncommon a project where I am involved that does not need to solve one or more of these problems. In this session I will give some real examples and resume options and recipes that can be used to solve those problems today in Drupal 7 and look to Drupal 8 to explain how it can improve some of our possibilities and options and easy the life of one of our most important personas: the content editor.
This document provides an overview of Drupal, an open-source content management system (CMS) that many libraries use to build and manage their websites. It discusses why libraries choose Drupal, gives examples of libraries using Drupal, outlines Drupal's system requirements and features, and describes the process of installing and configuring Drupal on different server platforms including Windows and Linux.
Oxford DrupalCamp 2012 - The things we found in your websitehernanibf
The document discusses various issues found on a website during an audit. It describes symptoms of problems with content architecture like duplicate content types and unused fields. It also outlines issues with site architecture such as custom modules that are not well designed or reusable, unnecessary complexity from unused features, and basic security vulnerabilities around outdated software, permissions, and injection attacks. The document provides guidance on how to further investigate and address these problems.
My Site is slow - Drupal Camp London 2013hernanibf
Drupal is a powerful and flexible tool to create web applications without building everything from scratch. This ability can drive developers to build complex websites without understanding what is Drupal doing behind the scenes.
The majority of Drupal performance talks mostly focus in aspects like infrastructure changes, caching strategies or comparisons between modules and architectures. Unfortunately when performance problems occur, development teams also follow strategies to replace different aspects of the platform looking only to standard aspects like slow queries without understanding and profiling the real problem.
The majority of times it is fundamental to measure and analyze what is the application is actually doing to understand te real problems. Drupal is a platform used by million of websites worlwide and its performance can in most cases be compared after measured.
In Acquia we do dozens of performance assessments per year, and even in most clients we find the same problems, often we find situations that only can be detected when measured and analized when looking to a profiler report.
In this session, I will explain how to detect performance problems looking to simple data, from logs to profiler data and providing some nice targets that can be analyzed to understand what is causing the uncommon bad performance of a site.
The document discusses the complexity of DITA (Darwin Information Typing Architecture). It explores both objective and subjective measures of complexity, including the number of parts and connections in a system. While DITA has many tags and features that could make it complex, the document argues that complexity depends on an individual's background and needs, and it can be managed by reducing specializations, using tools, and clearly defining roles. The speaker seeks audience input on how complex different DITA features seem and whether any parts seem too difficult.
This document summarizes the services and expertise offered by Acquia, a Drupal consulting firm. It discusses Acquia's Drupal and open source expertise, software industry experience, and the Acquia Network which provides Drupal support and optimized hosting. It also introduces the author and describes services like Drupal jumpstarts, workshops, audits, on-site consulting, and balancing custom and contributed code. The document emphasizes best practices in areas like content and display architecture, security, performance, infrastructure, maintenance, and deployment to help clients maintain a high-quality Drupal site.
The document provides an overview of Drupal for content creators. It discusses what Drupal is and how it can be used to build various types of websites. It covers basic Drupal terminology like nodes, menus, blocks, modules, and taxonomy. It also provides examples of setting up a simple homepage and menu structure for a new Drupal site.
We got to the point where the old Drupal mantra of creating content first to see it later is not enough to suceed with content editors. Drupal is competing and replacing other CMS and platforms where the lack of flexibility is the problem #1 for content editors. They are expecting full flexibity on how content is created, displayed, approved and published. However this introduce a common problem for web developers and site builders: how can you provide this full flexibility without having to be constantly on the hook for further development or configuration.
Modules like panels and panelizer, projects like Spark and distributions like panopoly and demo framework helped change the panorama in Drupal and the expectations that are set when sites are built.
In this session we will look to a set of common problems and real examples when creating content and layout for pages with demanding editorial teams. We will look and evaluate common options and recipes.
- How can complex content and rich pages be structured ? Free HTML format in different fields? Structured data in complex fields? Use paragraphs or field collection? Different content items in different items/entities? How to glue it all together?
- How can indivual page layout be managed providing flexibility but also control? Rely on templating system and view modes? Use contrib modules like panels and panelizer or display suite? Mix several approaches and modules?
- How can I add any content to any page and choose its display ? How can I have a list of curated widgets ready to use by the content team to deploy anywhere or in any section?
- How can pages and sections be managed before approved and published? Use prewiew systems and inline editors? Use workbench or workflow for layout? Rely on more complex content staging systems? Use separated environments?
These are daily problems that architects and developers face in every project. As a technical architect in Acquia it is uncommon a project where I am involved that does not need to solve one or more of these problems. In this session I will give some real examples and resume options and recipes that can be used to solve those problems today in Drupal 7 and look to Drupal 8 to explain how it can improve some of our possibilities and options and easy the life of one of our most important personas: the content editor.
Anatomy and Architecture of a WordPress ThemeJulie Kuehl
The document discusses the anatomy and architecture of a WordPress theme. It outlines the minimum files needed to create a theme, including index.php and style.css. It also lists common additional template files like header.php, footer.php, and sidebar.php. The document explains where themes can be found and installed on WordPress sites. It provides an example of the code needed in index.php and style.css. Finally, it discusses using folders to organize CSS, JavaScript, and image files that may be included in a theme.
Omeka: Open Archives and Exhibits for AnyoneJeremy Boggs
Omeka is open source web publishing software that allows users to create online archives and exhibits. It uses PHP and MySQL with Dublin Core metadata. Plugins add functionality and themes allow customization. Items have Dublin Core metadata and can have multiple files and tags. Users have different permission levels. Themes change the site appearance and plugins add features like exhibits and importing. Hosting is available on Omeka.net.
Content First – Planning Drupal Content TypesCarrie Hane
Content types make Drupal flexible. This presentation talks about how to define content types and why it is important to plan the CMS build by thinking about content first.
One Drupal to rule them all - Drupalcamp Londonhernanibf
Dries famous sentence (http://buytaert.net/one-drupal-to-rule-them-all) is becoming a reality for many organisations from small shops to the enterprise space. More and more stakeholders are following the idea of standardising their online presence in Drupal and leverage the same code and infrastructure amongst their different sites. What they are seeking is a drastic reduction in the time needed to create, launch and configure a Drupal site at the same time that they reduce the maintenance effort of the whole sites' network.
To achieve it, a drastic change needs to happen on the standardisation of development processes, more strict control of the overall architecture while supporting new changes and requirements, and repeatable and trustable deployment process to avoid the opposite pitfall of "one site to break them all".
In this session we will look to what needs to be thought when creating such an architecture from the development process to the infrastructure to host the different environments needed. We will look at different solutions that allow maintain these sites factories and walk you through several architectures explaining their advantages and differences.
Finally, we will look in detail to Acquia's Cloud Site Factory, a fully-hosted SaaS solution that allows organisations to quickly deploy and manage websites by the hundreds. Pre-define site templates, create new sites in a single click, manage roles and permissions across sites and connect to existing analytics and data systems.
This document provides an overview of an introductory workshop on getting started with the content management system Drupal, covering topics such as content types, themes, modules, users and permissions. The workshop aims to help attendees become more familiar with Drupal terminology and learn how to manage a basic Drupal site. Hands-on activities are included throughout to help attendees start using Drupal.
Drupal is a popular, open source content management system. It powers websites for governments, NGOs, communities, and businesses around the world. Drupal 8, the newest version, has recently been released and there are many exciting new features for end users, site builders, and developers.
If you're considering a platform for your next web development project, this webinar will give you a great opportunity to learn more about what Drupal has to offer.
This document provides information about an ePortfolio workshop for the PSA Art Program. It discusses how ePortfolios can exhibit student process, proficiency, progress, professionalism and be portable. It then outlines the steps to create an ePortfolio, including creating a content cloud on platforms like YouTube and Flickr, setting up a website using tools like Google Sites or WordPress, embedding content on the site, creating social media networks, and getting feedback through comments and analytics.
Using Omeka for setting up a dIgital library in the archives at Hunter Colleg...Judith Schwartz
Omeka is an open source web publishing platform that allows users like libraries, archives, and museums to create online collections and exhibits. It provides tools to upload and organize digital objects with metadata, build collection pages to display groups of items, create customized exhibits using themes and plugins, and add descriptive pages. Some advantages of Omeka include that it is free to use, has an active user community for support, and allows for flexible customization. However, it requires some technical skills to install and use without documentation or support.
Magnus Enger discusses his experience using and developing free/libre and open source software (F/LOSS) for Norwegian libraries. He summarizes several F/LOSS projects he has worked on, including Reaktor (a social network), Sublima (a subject portal tool), Pode (library mashups and linked data projects), and Glitre (middleware for Z39.50/SRU). He advocates contributing code changes upstream to benefit the wider community, and argues that F/LOSS allows libraries to experiment and adapt more quickly compared to proprietary software.
Museums, libraries, art institutes, and many other types of organizations need online exhibits - websites that mimic the experience of walking through a gallery discovering interesting and beautiful objects. Commercial museum collections management systems often provide this, but they are expensive and their features are often limited or require extensive customization. Open source exhibit software has proliferated in recent years, and some of these systems now provide features that approach CMS functionality. But what if you are starting with Plone, which is already a full-featured CMS?
Dumbarton Oaks Research Library and Collection is engaged in a major website redesign, and they have selected Plone as their CMS. Online exhibits will be an important part of their new website. They envisioned many features, such as image panning and zooming, timelines, favorites, and object comparison, and they also envisioned that online exhibits would be easy for content editors - even interns - to assemble. In this talk I will describe the online exhibit package that we have created for Dumbarton Oaks, and our incremental approach to defining and implementing it.
Drupal is from Mars, Wordpress is from Venus: Finding your library's CMS soul...sbclapp
Drupal and WordPress are the two most popular open-source content management systems. The document provides an overview and comparison of Drupal and WordPress, discussing their features including ease of use, community support, extensibility, custom content types, user roles, and more. Key differences are that Drupal typically requires more technical skills but allows for more complex, large-scale sites, while WordPress is very easy to use for small to medium sites through plugins and themes. The document aims to help libraries choose which system better fits their needs and capabilities.
Creating Dynamic Landing Pages for Drupal with Panels - WebinarSuzanne Dergacheva
Have you ever wanted to create a stand-alone campaign page on your website? Or prototype a new homepage layout just to see how it would look? The Panels module gives us the tools to build all kinds of landing pages in Drupal. Panels also has lots of other functionality, allowing you to create layouts and take control of how content is organized and displayed. All this, without having to write custom code.
In this webinar, we'll walk through some of the top use cases for Panels. We'll also talk about some best practices and things to avoid to make sure that you're using Panels effectively on your website.
- See more at: http://evolvingweb.ca/training/creating-dynamic-landing-pages-drupal-panels
This document introduces Drupal, an open source content management framework. It discusses Drupal's history and community, how it can be used to build and manage websites, and how its modular architecture allows for extensibility. Key points include that Drupal was founded in 2001, powers around 2% of websites, and has a large global community. Its core handles common site functions while thousands of contributed modules add additional features.
Drupal architectures for flexible content - Drupalcon Barcelonahernanibf
We got to the point where the old Drupal mantra of creating content first to see it later is not enough to suceed with content editors. Drupal is competing and replacing other CMS and platforms where the lack of flexibility is the problem #1 for content editors. They are expecting full flexibity on how content is created, displayed, approved and published. However this introduce a common problem for web developers and site builders: how can you provide this full flexibility without having to be constantly on the hook for further development or configuration.
Modules like panels and panelizer, projects like Spark and distributions like panopoly and demo framework helped change the panorama in Drupal and the expectations that are set when sites are built.
In this session we will look to a set of common problems and real examples when creating content and layout for pages with demanding editorial teams. We will look and evaluate common options and recipes.
How can complex content and rich pages be structured ? Free HTML format in different fields? Structured data in complex fields? Use paragraphs or field collection? Different content items in different items/entities? How to glue it all together?
How can indivual page layout be managed providing flexibility but also control? Rely on templating system and view modes? Use contrib modules like panels and panelizer or display suite? Mix several approaches and modules?
How can I add any content to any page and choose its display ? How can I have a list of curated widgets ready to use by the content team to deploy anywhere or in any section?
How can pages and sections be managed before approved and published? Use preview systems and inline editors? Use workbench or workflow for layout? Rely on more complex content staging systems? Use separated environments?
These are daily problems that architects and developers face in every project. As a technical architect in Acquia it is uncommon a project where I am involved that does not need to solve one or more of these problems. In this session I will give some real examples and resume options and recipes that can be used to solve those problems today in Drupal 7 and look to Drupal 8 to explain how it can improve some of our possibilities and options and easy the life of one of our most important personas: the content editor.
This document provides an overview of Drupal, an open-source content management system (CMS) that many libraries use to build and manage their websites. It discusses why libraries choose Drupal, gives examples of libraries using Drupal, outlines Drupal's system requirements and features, and describes the process of installing and configuring Drupal on different server platforms including Windows and Linux.
Oxford DrupalCamp 2012 - The things we found in your websitehernanibf
The document discusses various issues found on a website during an audit. It describes symptoms of problems with content architecture like duplicate content types and unused fields. It also outlines issues with site architecture such as custom modules that are not well designed or reusable, unnecessary complexity from unused features, and basic security vulnerabilities around outdated software, permissions, and injection attacks. The document provides guidance on how to further investigate and address these problems.
My Site is slow - Drupal Camp London 2013hernanibf
Drupal is a powerful and flexible tool to create web applications without building everything from scratch. This ability can drive developers to build complex websites without understanding what is Drupal doing behind the scenes.
The majority of Drupal performance talks mostly focus in aspects like infrastructure changes, caching strategies or comparisons between modules and architectures. Unfortunately when performance problems occur, development teams also follow strategies to replace different aspects of the platform looking only to standard aspects like slow queries without understanding and profiling the real problem.
The majority of times it is fundamental to measure and analyze what is the application is actually doing to understand te real problems. Drupal is a platform used by million of websites worlwide and its performance can in most cases be compared after measured.
In Acquia we do dozens of performance assessments per year, and even in most clients we find the same problems, often we find situations that only can be detected when measured and analized when looking to a profiler report.
In this session, I will explain how to detect performance problems looking to simple data, from logs to profiler data and providing some nice targets that can be analyzed to understand what is causing the uncommon bad performance of a site.
The document discusses the complexity of DITA (Darwin Information Typing Architecture). It explores both objective and subjective measures of complexity, including the number of parts and connections in a system. While DITA has many tags and features that could make it complex, the document argues that complexity depends on an individual's background and needs, and it can be managed by reducing specializations, using tools, and clearly defining roles. The speaker seeks audience input on how complex different DITA features seem and whether any parts seem too difficult.
This document summarizes the services and expertise offered by Acquia, a Drupal consulting firm. It discusses Acquia's Drupal and open source expertise, software industry experience, and the Acquia Network which provides Drupal support and optimized hosting. It also introduces the author and describes services like Drupal jumpstarts, workshops, audits, on-site consulting, and balancing custom and contributed code. The document emphasizes best practices in areas like content and display architecture, security, performance, infrastructure, maintenance, and deployment to help clients maintain a high-quality Drupal site.
The document provides an overview of Drupal for content creators. It discusses what Drupal is and how it can be used to build various types of websites. It covers basic Drupal terminology like nodes, menus, blocks, modules, and taxonomy. It also provides examples of setting up a simple homepage and menu structure for a new Drupal site.
We got to the point where the old Drupal mantra of creating content first to see it later is not enough to suceed with content editors. Drupal is competing and replacing other CMS and platforms where the lack of flexibility is the problem #1 for content editors. They are expecting full flexibity on how content is created, displayed, approved and published. However this introduce a common problem for web developers and site builders: how can you provide this full flexibility without having to be constantly on the hook for further development or configuration.
Modules like panels and panelizer, projects like Spark and distributions like panopoly and demo framework helped change the panorama in Drupal and the expectations that are set when sites are built.
In this session we will look to a set of common problems and real examples when creating content and layout for pages with demanding editorial teams. We will look and evaluate common options and recipes.
- How can complex content and rich pages be structured ? Free HTML format in different fields? Structured data in complex fields? Use paragraphs or field collection? Different content items in different items/entities? How to glue it all together?
- How can indivual page layout be managed providing flexibility but also control? Rely on templating system and view modes? Use contrib modules like panels and panelizer or display suite? Mix several approaches and modules?
- How can I add any content to any page and choose its display ? How can I have a list of curated widgets ready to use by the content team to deploy anywhere or in any section?
- How can pages and sections be managed before approved and published? Use prewiew systems and inline editors? Use workbench or workflow for layout? Rely on more complex content staging systems? Use separated environments?
These are daily problems that architects and developers face in every project. As a technical architect in Acquia it is uncommon a project where I am involved that does not need to solve one or more of these problems. In this session I will give some real examples and resume options and recipes that can be used to solve those problems today in Drupal 7 and look to Drupal 8 to explain how it can improve some of our possibilities and options and easy the life of one of our most important personas: the content editor.
Anatomy and Architecture of a WordPress ThemeJulie Kuehl
The document discusses the anatomy and architecture of a WordPress theme. It outlines the minimum files needed to create a theme, including index.php and style.css. It also lists common additional template files like header.php, footer.php, and sidebar.php. The document explains where themes can be found and installed on WordPress sites. It provides an example of the code needed in index.php and style.css. Finally, it discusses using folders to organize CSS, JavaScript, and image files that may be included in a theme.
Omeka: Open Archives and Exhibits for AnyoneJeremy Boggs
Omeka is open source web publishing software that allows users to create online archives and exhibits. It uses PHP and MySQL with Dublin Core metadata. Plugins add functionality and themes allow customization. Items have Dublin Core metadata and can have multiple files and tags. Users have different permission levels. Themes change the site appearance and plugins add features like exhibits and importing. Hosting is available on Omeka.net.
Content First – Planning Drupal Content TypesCarrie Hane
Content types make Drupal flexible. This presentation talks about how to define content types and why it is important to plan the CMS build by thinking about content first.
One Drupal to rule them all - Drupalcamp Londonhernanibf
Dries famous sentence (http://buytaert.net/one-drupal-to-rule-them-all) is becoming a reality for many organisations from small shops to the enterprise space. More and more stakeholders are following the idea of standardising their online presence in Drupal and leverage the same code and infrastructure amongst their different sites. What they are seeking is a drastic reduction in the time needed to create, launch and configure a Drupal site at the same time that they reduce the maintenance effort of the whole sites' network.
To achieve it, a drastic change needs to happen on the standardisation of development processes, more strict control of the overall architecture while supporting new changes and requirements, and repeatable and trustable deployment process to avoid the opposite pitfall of "one site to break them all".
In this session we will look to what needs to be thought when creating such an architecture from the development process to the infrastructure to host the different environments needed. We will look at different solutions that allow maintain these sites factories and walk you through several architectures explaining their advantages and differences.
Finally, we will look in detail to Acquia's Cloud Site Factory, a fully-hosted SaaS solution that allows organisations to quickly deploy and manage websites by the hundreds. Pre-define site templates, create new sites in a single click, manage roles and permissions across sites and connect to existing analytics and data systems.
This document provides an overview of an introductory workshop on getting started with the content management system Drupal, covering topics such as content types, themes, modules, users and permissions. The workshop aims to help attendees become more familiar with Drupal terminology and learn how to manage a basic Drupal site. Hands-on activities are included throughout to help attendees start using Drupal.
Drupal is a popular, open source content management system. It powers websites for governments, NGOs, communities, and businesses around the world. Drupal 8, the newest version, has recently been released and there are many exciting new features for end users, site builders, and developers.
If you're considering a platform for your next web development project, this webinar will give you a great opportunity to learn more about what Drupal has to offer.
This document provides information about an ePortfolio workshop for the PSA Art Program. It discusses how ePortfolios can exhibit student process, proficiency, progress, professionalism and be portable. It then outlines the steps to create an ePortfolio, including creating a content cloud on platforms like YouTube and Flickr, setting up a website using tools like Google Sites or WordPress, embedding content on the site, creating social media networks, and getting feedback through comments and analytics.
Using Omeka for setting up a dIgital library in the archives at Hunter Colleg...Judith Schwartz
Omeka is an open source web publishing platform that allows users like libraries, archives, and museums to create online collections and exhibits. It provides tools to upload and organize digital objects with metadata, build collection pages to display groups of items, create customized exhibits using themes and plugins, and add descriptive pages. Some advantages of Omeka include that it is free to use, has an active user community for support, and allows for flexible customization. However, it requires some technical skills to install and use without documentation or support.
Magnus Enger discusses his experience using and developing free/libre and open source software (F/LOSS) for Norwegian libraries. He summarizes several F/LOSS projects he has worked on, including Reaktor (a social network), Sublima (a subject portal tool), Pode (library mashups and linked data projects), and Glitre (middleware for Z39.50/SRU). He advocates contributing code changes upstream to benefit the wider community, and argues that F/LOSS allows libraries to experiment and adapt more quickly compared to proprietary software.
Developing video archive library using omeka : An open source digital library...Dhiren Panchal
The purpose of this paper is to aware LIS professionals and students about a Video library for educational video content using Open Source DLM Software - Omeka. This paper will
discuss about the importance of Video Library for developing new education serve platform,
within the context of Digital Media and Digital Library environment. Omeka has been
adopted by large number of Libraries and Museums at outside of India. This paper will
highlight the brief description of Omeka DLMS. And also focus in detail with how to create
Video Library using Omeka DLMS; which includes online exhibition, video archive and
connect with social networks.
This document provides information on various open source tools for libraries. It lists tools for web conferencing, desktop publishing, music libraries, screen casting, invoicing, surveys, public computer management, citation management, instant messaging, reference statistics, content management, blogging, online exhibits, OPACs, and course reserves. For each tool, it provides a brief description and link to the website. The document aims to introduce librarians to these free and open source software alternatives.
A basic overview of what Omeka is, when to use it, and how to use it. Omeka is a digital collections and exhibits platform used by museum professionals, teachers, librarians, and academics.
This document provides information about Omeka, a digital exhibit building software. It defines Omeka as a tool that enables users to create online exhibits showcasing collections of digital materials. It discusses when Omeka is and is not the right choice for a project. It also outlines the basic structure and vocabulary of Omeka, including items, collections, exhibits, and plugins. Steps for building an Omeka site including planning, adding items and metadata, and constructing exhibits are summarized.
This presentation summarizes various Web 2.0 tools that can be used for staff development and in the classroom. It provides the names and URLs of tools for creating online collaborations, organizing and sharing resources, creating speaking avatars, sharing stories and comments, authoring online courses, blogging, shortening URLs, creating online webs and mind maps, microblogging, creating social networks, creating desktop recording movies, guided presentations, editing wikis, sharing educational videos, presenting other materials online, creating animations, conducting surveys with pictures, and online image editing. Examples and similar alternative tools are also listed for some of the tools.
Omeka is an open-source digital publishing platform that allows users to publish archives, collections, exhibits and teaching materials for free. It has a simple interface that enables non-technical users to launch a site with five minutes of setup. Omeka also offers a strong community for documentation and support, and is highly extensible through custom themes and plugins. It supports a variety of file types, standards-based metadata, and allows content to be shared and reused across sites.
Getting Started With Omeka (DHSI 2015 Unconference)jkmcgrath
Slides from 2015 DHSI "unconference" session titled "Getting Started with Omeka." Slides are slightly tweaked / condensed from HASTAC Webinar slides used in early 2015 by Jim (see my SlideShare page for those slides).
Omeka is an open source digital repository platform that allows users to build online collections, exhibitions, and archives. It uses Dublin Core metadata standards and has plugins for functions like importing metadata in bulk. Omeka collections and exhibitions aggregate digital items and allow them to be organized thematically. The Neatline plugin integrates maps and georeferenced historical images into interactive exhibits. While Omeka is free, it requires technical expertise to install and maintain on a web server.
HASTAC Scholars: Omeka and Digital Archivesjkmcgrath
Slides from HASTAC Scholars webinar on Omeka and digital archives (February 20th, 2015). Link to webinar / notes forthcoming.
Thanks to HASTAC Scholars (and particularly to Fiona Barnett and Kalle Westerling) for the webinar invite!
I'm easy to find on Twitter @JimMc_Grath. E-mal: mcgrath[dot]ja[at]husky.neu.edu
Omeka is open-source software that can be used to create an online repository for learning objects (LOR). It has two main components - a public portal to display content, and a back-end area to store and manage materials. Content is added by uploading files and providing descriptive metadata. Omeka supports various file formats, collections, user roles, searching and embedding content on other sites. It provides options for both public and private access to materials.
This is a very basic workshop to introduce novice users to Omeka with an eye towards providing hands-on experience to decide whether it can serve their own research needs.
This document discusses Library 2.0 and new technologies that can enhance library services. It recommends that libraries learn from others, experiment with new technologies like blogging, podcasting, and social media. Libraries should also think about how to improve their online catalogs to better meet user needs and expectations of the "Google Generation". The document provides examples of innovative libraries and encourages libraries to think about new ways to provide learning spaces and services.
In 2015, I created a web archiving fundamentals course for the Society of American Archivists (SAA) Digital Archives Specialist (DAS) program. This is a portion of the slide deck I used for that course.
This document provides a list of online tools and resources for teachers and students to use technology in the classroom. It includes websites for wikis, online bookmarking, file sharing and storage, organizing resources, presenting materials, editing photos, podcasting, digital storytelling, interactive tools, and building vocabulary. Many of these free websites allow teachers to collaborate, share materials and lessons, and engage students through multimedia content.
The document discusses using Drupal to build an exhibition website, including how to install Drupal, create content like pages and menus, use modules, themes, content types and views to organize content, and leverage APIs and jQuery to add interactivity. It also provides recommendations for additional Drupal resources.
Final copyofopensourcesites softwareandpresentationoutlineforslideshowfinal5-...alysonkaye
This document provides an overview and outline of open source software options for libraries. It begins by clarifying the difference between open source software and freeware, noting that open source software licenses are open and customizable. It then lists several benefits of open source software such as reduced costs, increased flexibility, and improved security compared to proprietary options. While open source code can be modified, the document acknowledges that many libraries lack the time or resources to make changes. However, open source ensures that development will continue even if a specific organization stops supporting a project. The document provides numerous examples of open source software that libraries can use and concludes with a checklist for evaluating different open source products.
Strategies for Effective Upskilling is a presentation by Chinwendu Peace in a Your Skill Boost Masterclass organisation by the Excellence Foundation for South Sudan on 08th and 09th June 2024 from 1 PM to 3 PM on each day.
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...Dr. Vinod Kumar Kanvaria
Exploiting Artificial Intelligence for Empowering Researchers and Faculty,
International FDP on Fundamentals of Research in Social Sciences
at Integral University, Lucknow, 06.06.2024
By Dr. Vinod Kumar Kanvaria
A workshop hosted by the South African Journal of Science aimed at postgraduate students and early career researchers with little or no experience in writing and publishing journal articles.
A Strategic Approach: GenAI in EducationPeter Windle
Artificial Intelligence (AI) technologies such as Generative AI, Image Generators and Large Language Models have had a dramatic impact on teaching, learning and assessment over the past 18 months. The most immediate threat AI posed was to Academic Integrity with Higher Education Institutes (HEIs) focusing their efforts on combating the use of GenAI in assessment. Guidelines were developed for staff and students, policies put in place too. Innovative educators have forged paths in the use of Generative AI for teaching, learning and assessments leading to pockets of transformation springing up across HEIs, often with little or no top-down guidance, support or direction.
This Gasta posits a strategic approach to integrating AI into HEIs to prepare staff, students and the curriculum for an evolving world and workplace. We will highlight the advantages of working with these technologies beyond the realm of teaching, learning and assessment by considering prompt engineering skills, industry impact, curriculum changes, and the need for staff upskilling. In contrast, not engaging strategically with Generative AI poses risks, including falling behind peers, missed opportunities and failing to ensure our graduates remain employable. The rapid evolution of AI technologies necessitates a proactive and strategic approach if we are to remain relevant.
June 3, 2024 Anti-Semitism Letter Sent to MIT President Kornbluth and MIT Cor...Levi Shapiro
Letter from the Congress of the United States regarding Anti-Semitism sent June 3rd to MIT President Sally Kornbluth, MIT Corp Chair, Mark Gorenberg
Dear Dr. Kornbluth and Mr. Gorenberg,
The US House of Representatives is deeply concerned by ongoing and pervasive acts of antisemitic
harassment and intimidation at the Massachusetts Institute of Technology (MIT). Failing to act decisively to ensure a safe learning environment for all students would be a grave dereliction of your responsibilities as President of MIT and Chair of the MIT Corporation.
This Congress will not stand idly by and allow an environment hostile to Jewish students to persist. The House believes that your institution is in violation of Title VI of the Civil Rights Act, and the inability or
unwillingness to rectify this violation through action requires accountability.
Postsecondary education is a unique opportunity for students to learn and have their ideas and beliefs challenged. However, universities receiving hundreds of millions of federal funds annually have denied
students that opportunity and have been hijacked to become venues for the promotion of terrorism, antisemitic harassment and intimidation, unlawful encampments, and in some cases, assaults and riots.
The House of Representatives will not countenance the use of federal funds to indoctrinate students into hateful, antisemitic, anti-American supporters of terrorism. Investigations into campus antisemitism by the Committee on Education and the Workforce and the Committee on Ways and Means have been expanded into a Congress-wide probe across all relevant jurisdictions to address this national crisis. The undersigned Committees will conduct oversight into the use of federal funds at MIT and its learning environment under authorities granted to each Committee.
• The Committee on Education and the Workforce has been investigating your institution since December 7, 2023. The Committee has broad jurisdiction over postsecondary education, including its compliance with Title VI of the Civil Rights Act, campus safety concerns over disruptions to the learning environment, and the awarding of federal student aid under the Higher Education Act.
• The Committee on Oversight and Accountability is investigating the sources of funding and other support flowing to groups espousing pro-Hamas propaganda and engaged in antisemitic harassment and intimidation of students. The Committee on Oversight and Accountability is the principal oversight committee of the US House of Representatives and has broad authority to investigate “any matter” at “any time” under House Rule X.
• The Committee on Ways and Means has been investigating several universities since November 15, 2023, when the Committee held a hearing entitled From Ivory Towers to Dark Corners: Investigating the Nexus Between Antisemitism, Tax-Exempt Universities, and Terror Financing. The Committee followed the hearing with letters to those institutions on January 10, 202
Macroeconomics- Movie Location
This will be used as part of your Personal Professional Portfolio once graded.
Objective:
Prepare a presentation or a paper using research, basic comparative analysis, data organization and application of economic information. You will make an informed assessment of an economic climate outside of the United States to accomplish an entertainment industry objective.
How to Fix the Import Error in the Odoo 17Celine George
An import error occurs when a program fails to import a module or library, disrupting its execution. In languages like Python, this issue arises when the specified module cannot be found or accessed, hindering the program's functionality. Resolving import errors is crucial for maintaining smooth software operation and uninterrupted development processes.
Main Java[All of the Base Concepts}.docxadhitya5119
This is part 1 of my Java Learning Journey. This Contains Custom methods, classes, constructors, packages, multithreading , try- catch block, finally block and more.
2. Omeka is…
a “digital publishing suite for scholars,
librarians, archivists, museum
professionals, and cultural enthusiasts”
–Omeka team’s definition
a “system for storing digital objects
(photos, pdfs, video, etc.) and their
metadata, and creating digital
exhibitions around those objects” –my
definition
3. Why Omeka?
It’s free!
It’s open source!
It’s easy to use!
It’s easy to get started!
7. Sign up for a hosted site:
Omeka.net
Basic account is free
Tiered paid accounts include more
storage and customization options
Choose your own subdomain for each
site: [yournamehere].omeka.net
Admin interface is the same as in the
local version
23. What can you do with
Omeka (and its plugins)?
Create digital exhibits
Create digital collections
Make it your whole website (Simple Pages)
Map your items (Geolocation)
QR codes (Bar Codes and Reports)
Solicit and accept content (Contribution)
Student projects
24. HIST285 project
Research a technology at Drexel
Develop a thesis, and find supporting
material in the Archives
Create a digital exhibition in Omeka
27. Administrative stuff
One Omeka account per project group
One Omeka “expert” per project group
Specialized instructions
Specialized scan request form
Access to scans
28. Using Omeka for student
projects
Decide where the exhibits will live
Users need admin privileges to create
exhibits
Force students to read the instructions
Not part of the grade? They won’t do it
Copyright matters
Undergrads don’t think like archivists
Good research ≠ good exhibit
http://chronicle.com/blogs/profhacker
/teaching-with-omeka
29. Omeka is awesome!
…but not for everything
If you need a quick-and dirty way to put
content online…use a blog
If you need a quick-and-dirty way to put
images online…use Flickr
If you need a digital asset management
system…use ContentDM, or an open
source DAMS like ResourceSpace
30. What to do when you get back
to your archives
Omeka sandbox:
http://omeka.org/codex/
Try_Omeka_Before_Installing
Create a free hosted site:
http://www.omeka.net/signup
Watch the Omeka screencasts:
http://omeka.org/codex/Screencasts
Example Omeka sites:
http://omeka.org/showcase
32. Thank you!
Peter Ivanick set up the Drexel Archives
Omeka site
Kate Lynch customized the Drexel Archives
Omeka site
Ian Richmond set up my Omeka demo site
Rob Sieczkiewicz reviewed my slides (and
made an excellent zombie)
Many Drexel Libraries staff beta-tested my
presentation
33. Photo credits
Wooly opossum hanging by its tail, from the Field Museum:
http://www.flickr.com/photos/field_museum_library/3608438186
asparagus cheddar cheese omelet, by jgodsey:
http://www.flickr.com/photos/jgodsey/3378623493
Origami stellated octahedron, by endolith:
http://www.flickr.com/photos/omegatron/438272080
Sewing for a production, c. 1930s, from the State Library of New
South Wales:
http://www.flickr.com/photos/statelibraryofnsw/3273848716
All other photos: Drexel University Archives and Special
Collections
Editor's Notes
It’s o-MEH-ka, not o-MEE-ka. Rhymes with Rebecca
Not to be confused with an opossum, an omelet, or origami
Omeka is produced by the Center for History and New Media at George Mason University.
Quote is from the Omeka site: http://omeka.org/files/docs/Featurelist.pdf
I think the exhibits and metadata are pretty central to Omeka
It’s free, I think we can all agree that’s good.
Open source: you can customize it: write site and exhibit themes, write plugins, etc.
Easy to use: if you can update a blog, you can create an exhibit. And if you can’t figure something out, the Omeka website has good instructions and tutorials and forums
So easy, a cataloger could do it! Sorry…Anyway, it’s easy to get started, and you have a couple of options for how to do that
This demo site was set up by an IT person who had never installed Omeka before. He said it took him about an hour, and most of that time was spent waiting for things to install. The instructions on the Omeka website are very helpful.
Here’s the Drexel University Archives’ Omeka site, heavily customized by our web designer.
Here’s one of our customized exhibit pages
Omeka.net just went beta within the last couple of weeks
Omeka has really good video tours on their website, so I’m not going to try to walk you through the software. I just want to show what a site looks like out of the box, and then show you how easy it is to create content
Here’s the demo site I showed you before, but now it has some content in it. We recently had a zombie party in the Archives, so my site contains photos from that. There’s a search box for the site, and links to browse items, collections, and exhibits.
Browse items
If you click on an item thumbnail, you can see the item metadata, a larger version of the image, and a citation (generated automatically by the site)
Browse exhibits
Heres a page from an exhibit. There’s the exhibit title, the section title, and the title of the particular page. If you click on the thumbnail, you can see the item metadata for the photo.
Okay, now I’ll show you how I put all the content in there.
First, you need some items. Omeka uses Dublin Core, and you can decide which fields you want to use and configure your site not to display empty fields.
Items can have multiple files. This is a good way to present, say, multiple pages from a book, or two photos of the same 3D object.
Create an exhibit: give it a title, a slug (URL component), credits, and a description. You can also set your exhibit to be public or private, so you can keep an exhibit hidden until it’s finished
After you create an exhibit, you can add sections, and then add pages to those sections
Create a page: give it a title and slug, and choose a layout: lots of little images, one big image, no images all text, etc. Omeka comes with many layouts, but you can also write your own.
Once you choose a layout for your page, you can start adding items. Up top you’ll see thumbnails for all the items you’ve created. If your site has more than two items, click the Show Search Form link up top to search your items. To add an item to your exhibit, click its thumbnail and drag it down into an empty box, like this one on the lower right.
Add users, delete users, and give them a role, which determines how much they can edit on the site.
Download a theme from the Omeka site, upload it to the right directory on your website, and it’ll show up on the themes page, where you can select it to activate it. You can also write your own theme, and Omeka comes with a few themes pre-installed.
Like with themes, download them from the Omeka site and put them in the right directory. Need to click the button to install, may need to configure them (through the admin interface) before they work. Again, you can also write your own, and Omeka comes with a few pre-installed.
Now that I’ve told you how Omeka works, I’ll talk about what you can do with it
You can create digital versions of physical exhibits, expanded digital versions of physical exhibits, or standalone digital exhibits.
You can use create collections in Omeka to organize items—by archival collection, by theme, etc.
Make it your whole website: You can use the Simple Pages plugin to create pages (rather than exhibits) on your Omeka site.
Map your items: The Geolocation plugin lets you create a Google map of your items.
QR codes: QR codes are bar codes that a smartphone can read. You can put QR codes on a physical exhibit, in a brochure, anywhere you want, and link them to items in Omeka. Users can scan the QR codes and view your item pages.
Solicit and accept content: The Contribution plugin lets users contribute files and descriptions, which you can then turn into items on your site.
Student projects: Omeka is so easy an undergrad could do it!
If you were at SAA, you might have heard me talk about the HIST285 project before. This is a totally different presentation. I’m just going to focus on how we used Omeka for the project.
Here’s a HIST285 exhibit
Here’s another HIST285 exhibit. All this here isn’t exhibit text, it’s the junk you get when you copy text out of Word. As you can see, there was a range in the kinds of exhibits students created.
Each group was asked to choose an Omeka expert, who attended the training and received an account, but all members of the group were allowed to use the account
Specialized instructions: I wrote instructions that only explained how to use the parts of the site they needed to use, and that specified our requirements, like which metadata fields to fill out and what to put in them
Specialized scan request form: for each item that students wanted scanned for their exhibits, they had to fill out a form with fields corresponding to the metadata fields in Omeka. Some fields they had to fill out themselves before scanning, others were filled out by our scanning technicians, like the unique ID for the file
Access to scans: Drexel has a service called DragonDrop where you can create playlists of files for people to download. We created one playlist for each group and put all the scans they requested there.
Decide where the exhibits will live: Do you want them on your website mixed in with the rest of your exhibits? Or do you want to create a separate Omeka site for them? The answer probably depends on whether you’ll need to apologize for the content. We had a group make an exhibit that said “Women were known to be inferior to men” and although I don’t think that’s really what they meant, it was public on our website for a while.
Users need admin privileges to create exhibits: That means students can edit and delete content anywhere on the site. They could delete something by accident, or sabotage other groups’ work. Also, the site doesn’t prevent two people from editing the same content at the same time.
Force students to read the instructions: Like I said, students can do a lot of damage. Most students never read those customized instructions I wrote. Next time we’re going to make them take a quiz to prove that they read the instructions before we give them an Omeka account.
If they aren’t graded on it, they won’t do it: Students had to fill out the metadata fields on their scan request forms, but most of them didn’t bother to fill out the fields in Omeka, because they weren’t graded on it.
Copyright matters: Students aren’t used to worrying about copyright in their academic work, but if their projects are going on your public website, you need to worry about it. The first time we worked with HIST285, it hadn’t occurred to us that students would put images from outside the Archives in their exhibits. We have plenty of photos of the dorms in the Archives—why steal them from Wikipedia? The second time around, we threatened to delete any outside images we found unless students asked for permission first—they still did it. What if students want to use public domain images not from your archives? What if they want to use photos they took themselves? Decide on your policies ahead of time, and don’t feel bad about deleting content if students have fair warning—I never do!
Undergrads don’t think like archivists. They don’t share our sense of intellectual units—they might create two items to display two pages from the same book, or a single item to display two photos of the same person. They don’t understand why description is important, so they don’t provide any description beyond a title, and the titles are things like “Photo #6.” These are things you or the professor need to explain.
Good research =/= good exhibit: maybe the findings are interesting, but if the evidence is all from memos and meeting minutes, it could make for a really boring exhibit. Also, students are used to writing research papers, so they need to learn about how to write a good exhibit. If what they’re really writing is a research paper to be hosted online, Omeka is not the best way to display it.
ProfHacker has a really great post about using Omeka for student projects
Yeah, Omeka is awesome, and flexible, and easy to use…but not the best solution for everything
As ProfHacker points out in his blog post, metadata is pretty essential to Omeka. If you’re just trying to put text and/or images online, there are easier ways.
Yes, Omeka stores files and metadata. If you need to manage a small number of digital assets, it might be okay. But you can’t do a lot of batch editing, or provide different levels of end-user access, or manage any sort of workflows.
We don’t have a DAMS at Drexel yet, but when we get one our plan is for it to supplement Omeka, not replace it. If your DAMS can export CSV, you can import from your DAMS into Omeka using the CSV import plugin
Whenever I go to conferences, I always see demos of software that sounds awesome, and then I get back to the archives and realize I have no idea what to do next. So, if Omeka sounds like it would be useful to you, here’s what to do when you get home:
Play with the Omeka sandbox. This is a test account that already has items and exhibits in it, and the whole site is refreshed every 24 hours, so you can’t do any damage.
You can create a free account on Omeka.net, which includes one Omeka site that you can play with.
Watch the Omeka screencasts at http://omeka.org/codex/Screencasts
Check out how other institutions are using Omeka at the Showcase
Contact me! I’d be happy to do a screencast and show you what using the site is like.