Creating a Worldwide Digital Heritage with EM9

June 17, 2016 6:54 pm

 

How do we capture knowledge?

In his TED talk, president and lead application developer of EnterMedia, Christopher Burkey describes the global need for the fair use of technology and regional databases of knowledge that belong to everyone.

Burkey describes the historical evolution of knowledge, from oral to physical knowledge, and our current shift to digital knowledge. Because our history and culture as a society is now stored primarily as digital knowledge, he notes there is a great importance for maintaining public control over that data rather than storing it in a profit driven corporate cloud. Corporate clouds and social media subject our data to terms and conditions, apply restrictions to how we use our own content, and even license it back to us. As we grow our knowledge pools, it is of growing importance to be conscious of who is the caretaker of that data.

Whether the motive is to use that knowledge for profit or the good of society is also important to consider, especially if we hope to allow future generations to access knowledge that are free of restriction or censorship via corporate or political policies.

Regionalism is also a necessary focus, especially as we strive to maintain our both global and regional heritage. Varying database solutions with individual controls allow for communities to have appropriate management over how they store their data and not lose the individualism of culturally based data, therefore maintaining diversity.

In closing, we are asked to challenge ourselves to consider how we as a society are building effective knowledge centers for ourselves, our communities, and our work.

Use an Open Source Media Database

EnterMedia 9.0 was recently released to meet the need of a world wide user base. Key features include:

  1. Easy Deployment RPM repository and installer on CentOS, RedHat or Ubuntu based servers
  2. Multi Language Assets The United Nations is using EnterMediaDB to publish in nine different languages worldwide.
  3. User Collections Greater compatibility with design applications including InDesign and Photoshop. Increased ability to sync changes and upload complex files or folders of files, as well as ability to edit this media straight in the database.
  4. Low Cost Hosting EnterMediaDB.net features low cost disk storage and scalability that can be moved to in-house at any time

Worldwide Deployments

Key deployments involve many large educational institutions including Harvard, Yale, University of Michigan, SDSU, Mohawk College and Weatherford College.

Non-profits are also deploying knowledge dabatabases, including Radio Canada, Mindset, Oceano, and Museumsdorf Cloppenburg

To build a digital library of your own, downloads and hosting are available at EnterMediaDB.net and EnterMediaDB.org.

Metadata Best Practices

March 23, 2016 4:55 pm

Complying with metadata best practices can keep the DAM UI clean and relevant to the needs of users. Here is a shortlist that every admin should know:

1.) Require fields – Required fields cannot be left blank when a user is adding new information or modifying existing metadata. The web upload page is a great place to add multiple required fields. This will ensure that no media can be uploaded without basic information.

2.) Use controlled vocabulary – Single select lists and multi select lists can be used to keep users from misspelling terms or labeling media in obscure ways. This will keep terminology consistent and predictable throughout the application. Permissions can be specific user profiles that allow them to add list values on the front end of the application.

3.) Promote key fields – Key fields, like tags, should be accessible in multiple areas throughout the application. Making them available in the Advanced Search area or Filters, will make it easy for users to search based on these fields. Placing them in the table view makes it easy for users to identify that search results meet their specific criteria. Lastly, make sure the fields are featured in General, File Properties, or some other custom metadata view.

4.) Keep it Simple – Sometimes less is more. By focusing the UI and related workflows on core content, administrators can create a more intuitive environment. Advanced fields, department specific fields, or other exceptions, can be placed in permission based data views so they don’t interfere with the process of other users. Users can be given permissions to add additional search terms, table result fields, and data views as their workflow requires.

5.) Take advantage of granularity – Specific fields allow users to be intentional with results. Having designated fields for locations, dates, stakeholders, history, rights usage, etc.. can be very useful up front and over time. Relying too heavily on a field like tags can become chaotic. Useful Information can get lost in the clutter of unrelated terms.

6.) Automate information – Sometimes metadata, such as product number, is written into a filename or a folder name. EnterMedia can be customized with scripts that can be taught to extract or assume information based on other context clues. As long as there are consistent variables to build from, automation can be used to save a lot of time and effort when labeling assets.

7.) Dedicated data views – Most DAM systems will support dedicated data view. Some categorical examples are:physical properties, rights management, and business information. Dividing metadata into these types of areas makes it easy for users to find desired data. Admins should be able to add and customize data views as requirements change.

Metadata example

A more detailed article about metadata best practices is available in our knowledgebase.

EMBridge (Drupal) and EnterMedia at The University of Mighigan – Flint Campus

February 26, 2016 7:08 pm

DPCI is one of EnterMedia’s oldest and most trusted partners. They developed EMBridge to connect the EnterMedia DAM to the Drupal CMS and vice versa. Customers like The University of Michigan – Flint Campus are a great example of how value added resellers, like DPCI, can walk a client through the challenges of transition from one solution to another.

EMBridge and EnterMedia for UM-Flint

“When UM-Flint came to DPCI, the University Relations department was using a proprietary digital asset management (DAM) system to store and manage tens of thousands of media files. UM-Flint staff was dissatisfied with the functionality and implementation of the DAM system as well as the software’s annual cost. UM-Flint also wanted to revamp its metadata schema to better categorize image files so that they were easier to find and reuse. In addition, the University website, built on top of Drupal CMS, had no connection to this DAM to access images for publishing on the website.”

The full case study is available on the DPCI site: http://www.dpci.com/case-studies/digital-asset-management/university-michigan-flint-campus

UM-Flint has now been using EnterMedia for over a year. They maintain a support agreement with us EnterMedia and have significantly reduced their overhead costs. EnterMedia continues to focus on the higher education and non-profit markets as a low cost alternative to proprietary solutions. More information is available at LearningMediaDB.com.

WordPress – EnterMediaDB Plugin

February 16, 2016 9:48 pm


EnterMediaDB has developed a plugin for WordPress that allows you to publish content directly from the DAM to one or more WordPress sites. The plugin is available on GitHub. Begin by cloning the EnterMediaDB-EML project, then zip the latest entermediadb plugin folder. Once this is complete you can upload the package to your site via the plugins interface. 

You should be able to view the plugin on your list, and manage the details under Settings/ EnterMediaDB. 

There are three pieces of information that must be entered here.

  1. The Access Key – this will need to be configured by the user. It can be anything but must be identical to the Access Key used in the WP Publishing profile on your EMShare site.
  2. MediaDB Application ID – this value will correspond with catalogsettings/mediadbappid in your EMShare application. You can find this area by going to Settings/Data Manager/catalogsettings/mediadbappid
  3. CDN Prefix – if you have one, you can enter it here. Otherwise enter the URL for your site without the trailing slash. For example: http://emsite.entermediadb.net

Once the information on the WordPress side is entered, you can build the profile on the EMShare site. Go to Settings/ (Asset Settings) Preferences/ Publishing. Here you will find some suggestions for publish locations. There will be one for WordPress. Select it and enter values for:

  • Description – this should be an easy way to differentiate your site from other WP sites
  • MediaDB Application ID – this value will correspond with catalogsettings/mediadbappid in your EMShare application. You can find this area by going to Settings/Data Manager/catalogsettings/mediadbappid
  • CDN Prefix – if you have one, you can enter it here. Otherwise enter the URL for your site without the trailing slash. For example: http://emsite.entermediadb.net

Now that things are set up on both sides you can test publishing by selecting media, then choosing Share/ Publish/ WordPress (or whatever description you have entered).

Let us know if you have any questions!