Setting up Omeka on IU s Webserve

Setting up Omeka on IU s Webserve Request Webserve Account Consult the "Getting Started" document before you request a Webserve account. The following steps are required: 1. Request a Group Account 1. Select a username that is descriptive of your project 2. You will be able to share the username and passphrase with project team members 2. Create a Webserve Account 1. Complete a short form be prepared to provide a description of your project 2. It may take 2-3 days to confirm your Webserve account after you apply 3. Create a Webtest Account if you think it would help to have a dev/test environment (Webserve is production Webtest is dev/test) 4. Create a MySQL account (required for Omeka) 1. When you apply for a MySQL account, you will receive a questionnaire to answer over email. Below are guidelines in orange for how to respond (*asterisks indicate required responses):! Additional Email Address: You may want to enter an additional email address for Webmaster notifications, but the owner and contact will receive official communication.! * Service Description: Please provide a description of the institutional purpose and the type of information and services that you wish to provide through this service (required) 1. Whatever the purpose is. Often individual faculty, staff or student research. Recycle description provided for Webserve account request. 2. Example: I will be using a Webserve account to host my digital research project, NAME OF PROJECT, which will use the open-source Omeka web publishing framework that relies on a mysql database (http://omeka.org/codex/preparing_to_install).! * Peak Hits: Provide an estimate of the number of peak accesses from your web application(s) per minute during its heaviest period of use. 1. 12 to 20 (depending on public interest)! * Maximum Size: Provide an estimate of the maximum size (in megabytes) that your database will attain. 1. 50-200 MB (depending on the size and type of your digital collection audio and video files will take more room)! * Sensitive Data?: Will personal or sensitive information be collected and placed into the database? Find information about sensitive data 1. Yes No Almost always "No" unless your research is collecting and storing specific information about individuals or other sensitive data.! Details about Sensitive Data: If you answered yes, please provide details about what sensitive information you will be collecting.! Encryption?: If you answered yes, will the sensitive data be stored encrypted and retrieved decrypted?! * Security Measures: Describe the security measures that will be taken to safegaurd the data (such as a security scan). 1. Not storing sensitive data but will follow IU's IT policies and security standards.! * Backups: Do you understand that you are responsible for performing your

own database backups and that a restore done by UITS may be insufficient to restore your database? 1. Yes No Yes! * Details: Information on database backups can be found in the Guidelines & Responsibilities section of the MySQL user guide. Please provide details of your backup strategy 1. Regularly schedule dumps of all tables in DB. (you can use myphpadmin to do this)! * 3rd Party Software: Do you intend to use your MySQL account with third party software such as a Content Management System (e.g. Drupal, Joomla), a bulletin board/forum, or a blog? 1. Yes No Yes, with Omeka as described above.! Details: If so, which product(s) will be used? Where can we obtain information about the product? 1. Omeka, http://omeka.org! * Access Information: How do you wish to receive the access information for your MySQL accounts? 1. By phone By Campus Mail I generally choose Phone (quicker).! Address: If you chose"by Campus Mail", the address must be for an office located on campus, not an email address. Providing an incorrect or an off campus address will significantly delay the process of receiving account information. 15. 2. Someone from the IU Webmaster Office will call your MySQL login for both test and production accounts 5. Create a Streaming account if you need video or other multimedia access. The remaining steps, 6-7, are optional, and should be decided by the PI. Setting up MySQL 1. Read the MySQL documentation if you have never worked with MySQL before. 2. Log into your account at mysql.iu.edu with the username and password provided by IU Webmaster (Webserve). 3. Type mysql -u root -p to log into your MySQL instance as the root user. You will be prompted for the root password on the next line this was provided to you by Webserve and is different from the password used to login to your account. 4. Once you are logged in as root, type CREATE DATABASE `omeka` CHARACTER SET utf8 COLLATE utf8_general_ci to create a new database called "omeka" configured to Omeka's standards. 5. Create a new user by typing CREATE USER username@'129.79.78.%' IDENTIFIED BY 'password' (Change username and 'password' to something memorable). 6. Give the new user proper privileges to modify the new database by typing GRANT select,insert,update,delete on omeka.* to username@'129.79.78.%' identified by 'password' (once again, change 'username' and 'password' to whatever you chose in step 5). 7. Update the database by typing FLUSH PRIVILEGES

8. Write down the host name (mysql.iu.edu), the database name (omeka), and the username and password you created in step 5 and save it somewhere. You'll need it later. 9. Log out of mysql.iu.edu, and log into your main Webserve account at webserve.iu.edu. 10. Follow the instructions in Webserve's phpmyadmin Setup Guide. When editing the 'config.inc.php' file, use the port number assigned to you by IU Webmaster (Webserve) and the information you recorded in step 8. After entering the proper information and saving, you should now be able to access phpmyadmin. Use https://www.indiana.edu/~usename/phpmyadmin/ to access phpmyadmin, substituting your webserve account name for the username. Don't forget the '~'. 11. If you are having trouble accessing phpmyadmin, consider the following options: 1. Make sure you have "https://" at the beginning of your URL. Leaving the protocol out of your URL defaults to HTTP, and phpmyadmin only works with HTTPS. 2. If you are getting an "Authorization Required" message, you are logged into an IU computer under your personal account. Add your username to phpmyadmin's.htaccess file (this is covered in step 3 of the phpmyadmin Setup Guide). 3. If you get a screen that says #1045 - Access denied for user 'username'@'lux.uits.indiana.edu' (using password: YES) or something similar, you have a mistake in your 'config.inc.php' file. 4. If you are getting some other error, contact Webserve. 12. Backups and File Restores You are responsible for performing and maintaining your own backups on mysql.iu.edu and mysql-test.iu.edu. 13. All accounts are pre-enabled for cron to permit you to run automated database checkpoint and backups. We strongly recommend doing a DB-level checkpoint mysqldump to ensure your data is backed up sufficiently should you need to restore data. While UITS performs standard system backups, because of the relationship between data elements within the data files needing to be in complete synchronization, a file restore done by UITS may not be sufficient to restore your database. For additional information see Backup and Recovery in the MySQL Reference Manual and the IU Webmaster document on MySQL backups. 14. Download and Install Omeka Go to the Omeka site and download the most compatible release. By this, we mean make sure that any Omeka Plug-ins you intend to you use (a common one is CSV import among others) are version compatible with the Omeka version you wish to install. Uncompress it and copy the Omeka directory to the www directory of your account on Webserve using secure FTP software. webserve.iu.edu port: 22 In the root directory of your Omeka Install is a file called "db.ini". You need to edit that file changing the X's to values specific to your setup.

Lines 14-16 contain the username and password that you created to access the database you created in the previous step. Line 17 has a prefix value that is prepended to the name of each table in the database. This can be any short string you want, like "prjt", "wgc" and so forth. (in newer versions of Omeka this line is already set to "omeka_", do not change this unless you have a good reason). Line 19 has the port number, normally a 4 character value. You will need to check for the port number in phpmyadmin which will tell you the value to use for you account. It generally follows the server name in the server field on the first page of phpmyadmin tool. Make sure the line is not commented out, it should not begin with a "" Database Configuration File Omeka requires MySQL 5 or newer. To configure your database, replace the X's with your specific settings. If you're unsure about your database information, ask your server administrator, or consult the documentation at <http://omeka.org/codex/database_configuration_file>. [database] host = "localhost" username = "XXXXXXXX" password = "XXXXXXXX" dbname = "XXXXXXXX" prefix = "XXXXXX" charset = "utf8" port = "XXXX" There are a few more changes you need to make to make Omeka work on IU Serve. If you get a Mod_rewrite error with Omeka on webserve. Mod_rewrite setup To make sure mod_rewrite is working, you need to add a line to.htaccess in the Omeka root directory that reads: RewriteBase /~yourusername/omekadirectory/ Replacing yourusername with the name of your web serve account and omekadirectory with the directory where you installed Omeka. Usually, since this file begins with a "." you will need to edit the file at the command line using ssh in a Terminal window on Macs or using putty on Windows machines. You should follow these steps:

1. SSH to webserve.iu.edu 2. Use your account's name and passphrase to log in. 3. Move to your www directory by typing cd www at the Unix prompt. Then cd to the directory where you installed Omeka. 4. To list the files in your www directory, type ls at the Unix prompt. 5. To edit a file, type the name of the editor you wish to use, followed by the file you wish to edit. For example, to edit a file named '.htaccess' using the nano editor you would type "nano.htaccess" The following step is not necessary with Omeka 2.0. There is only one.htaccess file and it is in the Omeka base directory. There is no.htaccess file in the install directory. If installing Omeka 1.5.x you will need to make the following changes Finally, to do the Omeka install for Omeka 1.5.3, you will need to add this line to the.htaccess file in the install directory of Omeka. Usually after a successful install you remove this directory. Basically you are making sure that Omeka install can see mod_rewrite so you add a line similar to the above line but that has the install directory as well. So you add the following line to.htaccess in the install directory: RewriteBase /~yourusername/omekadirectory/install/ Replacing yourusername with the name of your web serve account and omekadirectory with the directory where you installed Omeka but just keeping "install" the same. This is the default name for the install directory. Follow the steps as outlined above. Now the actual install Use the same procedures for installing Omeka 2.0. Once these changes are done, in a Web Browser go to http://www.iub.edu/~yourusername/omeka- 1.5.3/install/ or http://www.iub.edu/~yourusername/omeka-2.1.1/install/ Replace yourusername with the name of your web serve account and omeka-1.5.3 or omeka-2.1.1 with the directory where you installed Omeka but just keeping "install" the same. This is the default name for the install directory. Omeka should now connect to the database, create the tables it needs and setup your install of Omeka. You can now go to http://www.iub.edu/~yourusername/omeka-1.5.3/ or http://www.iub.edu/~yourusername/omeka-2.1.1/for the public site and http://www.iub.edu/~yourusername/omeka-1.5.3/admin or http://www.iub.edu/~yourusername/omeka- 2.1.1/admin to administrator the content and configuration of your Omeka site. Again replace yourusername with the name of your web serve account and omeka-1.5.3 or omeka-2.1.1 with the directory where you installed Omeka.

CSV Import Plugin Issues Issue 1: Error: The configured PHP path (/usr/local/bin/php) does not point to a PHP-CLI binary. You will get this error if your PHP binary has not been compiled with PHP-CLI included. If you are using Webserve to host Omeka, you need to go to your Omeka installation, go to the application/config directory and edit the config.ini file. Look for background.php.path= "" It is probably blank. You will need to make it use a specific php file so change that path to /usr/local/php5.4.16/bin/php background.php.path="/usr/local/php5.4.16/bin/php" If IUTS changes Webserve and the release of PHP, you may have to change this path. Issue 2: Error: Import settings expired. Please try again. This is generally caused by UTF-8 characters embedded in text in the CSV file. If you have saved that file using Excel, it does not do a particularly good job of handling UTF-8 unless you specifically tell it to during the export. I suggest that you download and use OpenOffice (free and open source). The spreadsheet app does a much better job of saving UTF-8 characters than Excel. Just save as a.csv file and then use that file when you browse for a file in the CSV plugin. Issue 3: Error: File being processed just freezes in the status queue. The CSV Import plugin can, on occasion, interfere with or be interfered with by other plugins. One way to fix this is to deactivate those plugins, but this will sometimes cause fields you are using to be unavailable. Another way to handle this is to edit application/config/config.ini. Look for and change jobs.dispatcher.longrunning = "Omeka_Job_Dispatcher_Adapter_BackgroundProcess" to jobs.dispatcher.longrunning = Omeka_Job_Dispatcher_Adapter_Synchronous" This will attempt to load the CSV file as one single process instead of running it in the background. It seems that running it in the background will often interfere with other plugins. If you have a very large csv

file, it may time out but I have typically loaded files with a 100 items without problems. In fact, I would suggest breaking files down to a smaller number of items when loading through CSV because it becomes easier to backout the items that may have a problem and to try again, rather than doing that with say a 1000 items at a time. The disadvantage of running in Synchronous mode is that when you select a file and then choose the mapping and then choose "Import CSV File", you will not be taken to the Status page until all the items are imported. This is also true if you back out an imported file. You must wait until all rows are processed. So I would suggest only making this change if necessary. URLs of Interest Omeka http://omeka.net/ http://omeka.org/download/ Omeka Plugins http://omeka.org/add- ons/ Account http://webmaster.iu.edu/getting- started/index.phtml http://webmaster.iu.edu/kb/apply- group- account.phtml Mysql http://webmaster.iu.edu/tools- and- guides/mysql/index.phtml http://webmaster.iu.edu/tools- and- guides/mysql/phpmyadmin.phtml