It seems like just yesterday we were in Los Angeles with an awesome crew of folks talking all things Domains, but time flies when you are reclaiming the web one site at a time! We are really excited to announce our Spring roadshow that will take place May 7th and 8th at Bryn Mawr College. You can find out more and/or sign-up for a spot over on the Roadshow website. We even have a draft of the two-day schedule up for your perusal. Keep in mind day 1 is geared toward Domain of One’s Own admins and costs $450 to attend, while day 2 is free and open to folks who want to share the work happening at their school, or even learn more about this whole Domains thing. Day 2 is organized so that everyone can both share and learn from other DoOO schools, and generally explore the limits and possibilities on and across campuses.
This week, Reclaim Hosting is running our second Workshop of One’s Own, where we will work with Domain of One’s Own admins to teach them about running DoOO on their campus. I’ve been tasked with talking through one of our most popular platforms, Omeka. While WordPress still takes the cake for the most popular applications run on our servers, Omeka has become increasingly popular. This post will dive into what Omeka is, and what you can do with the platform, and showcasing a few examples of how the platform could look when built out fully. You can read more about the other applications we are showcasing, Grav and Scalar. I’ve worked with Omeka for a little while but only when troubleshooting issues to specific sites, I haven’t built out a site like Omeka before. I took this a chance to look at the site in depth.
Omeka is a free open-source web-publishing platform. While it is open for anyone to use, the platform is mainly used by libraries, museums to archive items within their collections. The developers wanted to create a platform that allowed groups like this to create their own archive of collections just as easily as someone could start a blog. Omeka started with the development of Omeka classic, then the developers launched Omeka S, a standalone version similar to Omeka Classic. Omeka S has the option to streamline sites and more management features than Omeka Classic. Omeka allows institutions like this to create online exhibits to archive any topic. It has a relatively simple user interface– once you get the hang of the layout, it’s fairly easy to use. You’ll do most of the site building through the dashboard:
The main source code is standardized for each site but it is highly customizable based on themes and plugins used to build out the site. You can read more about installing themes and plugins on our Workshop of One’s Own website.
While I’m here, I’ll talk about three Omeka sites that are great examples of building out Omeka to archive events throughout history. The first is the Cork LGBT Archive. This website ‘aims to preserve, digitise, share and display information related to the history of the LGBT community in Cork, Ireland.’
This site showcases several exhibits of events within the LGBT community, building off of Arthur Leahy’s collection that began in the 1970s. One particular collection that stood out to me on this site was the Gay Sweatshop- Blood Green Collection. This archive a two-night play called ‘Blood Green’ that was put on by the Gay Sweatshop, at the Granery Theater. In an item within the collection, that describes what it was like to get the play up and running.
Another great example of Omeka, is Making Modern America: Discovering the Great Depression and New Deal. This is was created during a class offered at the University of Oklahoma in the Fall of 2015. The course examined what happened during the Great Depression and the New Deal. Students created this instance of Omeka to curate what happened in Oklahoma during that time, and many chose to continue the project after the class finished.
One thing that stood out to me is how the incorporated maps within their collection. This provides a great visual tool to document where things took place rather than documenting each item through exhibits. The class also added their lesson plans to the site through PDF embedding.
The last example I’ll talk about today is Georgetown University’s slavery archive. This was created as an effort to document Georgetown University’s involvement in the institution of Slavery. But what’s unique about this specific project, is the blend of WordPress and Omeka. When you got to slavery.georgetown.edu, you’re brought to a WordPress site that shows what the project is and what they’re working on to document this portion of history.
But, the main archive uses Omeka. The slavery archive really goes into detail about how Georgetown and the surrounding area was involved with slavery. The collection itself is a repository of materials related to the Maryland Jesuits, Georgetown University, and Slavery in the surrounding areas.
There are so many ways to use Omeka and to document pieces of history. These three sites are great examples of how you can document specific communities and periods of history around the world, specifically the LGBT community in Cork, Ireland, the New Deal in Oklahoma, and slavery at Georgetown University.
Changing ownership of a web hosting account in WHMCS is surprisingly simple. But why would you want to do this? Well, say for example a student or faculty was running a club or research site and they want to pass the ownership on to another person. As of now you still cannot have multiple admins on a cPanel account (we do hope this comes soon!), so you would have to transfer the account to the new owner. Assuming the user you want to transfer the account to already has an account in WHMCS, all you would need to do is go to the Product/Services tab for the hosting account you want to move and click the Move/Transfer button.
After that, a window will pop-up asking you to add the user’s client ID number that you want to move the account to. Once you do that and click transfer you are all done. It is really that simple. You might want to Resend the Welcome Email to the new user, but that should be all.
A simple, but useful bit on WHMCS is re-sending product emails. In this instance almost always product means web hosting given that is really the only product you would provide save for a domain depending on your school. Also, the only email you would really need to resend is the Welcome Email with their FTP credentials and other details. To do this login to WHMC and search for the user in the search box in the upper right-hand corner. Once you have found them, navigate to the Products/Services tab.
After that, at the bottom of that page there is a drop-down menu for re-sending email templates, you would want to re-send the “Hosting Account Welcome Email.”
This can also be done from the Emails tab by clicking the email button next to the “New Account Information” email:
After that they should have been sent another copy of their Welcome email.
When supporting Domain of One’s Own, on e of the issues folks run into is someone having created an account they not longer want. This can happen for several reasons: they think Facebook is the one true web, they believe aliens invented the internet and are using it against humanity (distinct possibility), they don’t like the domain they created, they have done their work and want it gone, etc. Probably the most common is someone created a domain they no longer want, and would like a new domain new. If they have content on the site, this would be better done by changing the domain in WHM. But, if the account is empty, and they just want to start over, we can terminate their hosting account in WHM through WHMCS, and then delete their WHMCS account. NB: It is important that both are done on order for folks to start anew.
Terminating the WHM account through WHMCS is only half the battle. Once that is done, the WHMCS account for that user most also be deleted (assuming they only had one hosting account that is now terminated) given when they try and re-create a domain from the Dashboard page in WordPress the system will only let them create a new account if there is no trace of them in WHMCS. This is one way to prevent users from creating multiple web hosting accounts.
Once the WHMCS client is deleted there will be no more sign of that user in WHM or WHMCS, so when they login through the Domain of One’s Own portal, they will have a clean slate. Keep in mind this is not recommended if the user already has created content given terminating the web hosting account will delete all their content.