Omeka – Reclaim Hosting https://www.reclaimhosting.com Take Control of your Digital Identity Thu, 08 Sep 2022 18:51:53 +0000 en-US hourly 1 https://wordpress.org/?v=6.5.4 https://www.reclaimhosting.com/wp-content/uploads/2018/09/RHprofilelogo-100x100.png Omeka – Reclaim Hosting https://www.reclaimhosting.com 32 32 Professional Development: Activating Omeka User With Our Password Reset Email https://meredithfierro.com/professional-development-activating-omeka-user-with-our-password-reset-email/ Mon, 28 Mar 2022 21:05:00 +0000 https://meredithfierro.com/?p=2802 Recently, I’ve found that I’ve needed access to an Omeka admin dashboard without a previous admin user on the site. Installatron makes it easy to log into sites like WordPress automatically but they don’t offer this option within Omeak or other applications.

We’ve been able to figure out a way to access the site through the dashboard directly from the database. This method relies on receiving an email reset to confirm the password, but what happens when you don’t receive the email? Well, let me teach out!

Omeka Login

Once you’ve added the user to the Omeka database following the steps listed above, you’ll want to request a password reset.

This generates a user activation link that we’ll need to get to the password reset screen. Once you have the login email, you’ll want to move to the database in PHPMyAdmin.

PHPMyAdmin

In PHPMyAdmin, you’ll want to navigate to the users table. We’ll need to get the user ID of thecurrent user you just requested the password reset for.

In this case, it’s user ID 1, but it may be different for your install.

 

Next, navigate to the users_activations table. This table holds all the active Password resets for each user.

You’ll want to grab the text in the URL box next to the corresponding user_ID we got from the users table. Make sure you’re looking at the user_id section on this table as the id might be the same.

 

In the Browser

After you have that URL snippet, you’ll want to move back into the browser. We’ll need to craft out the URL from the Omeka site. You’ll go to the admin login, in this case, mine is currently at https://reclaimtest.meredithfierro.com/admin. Next you’ll want to add the code /users/activate/u. This will create part of the password reset link. Finally, add the URL box we got from the users_activations table. So the full URL should look like this: https://reclaimtest.meredithfierro.com/admin/users/activate/u/1140c618248acc34c9bdb924eafae99b62622b80.

Then load the page and you should see the password reset!

 

This method is super handy to get access to help troubleshoot, especially if you want to prevent back and forth between the person. I’m all for limiting any unnecessary communication.

 

]]>
Professional Development: Activating Omeka User With Our Password Reset Email https://meredithhuffman.com/professional-development-activating-omeka-user-with-our-password-reset-email/ Mon, 28 Mar 2022 21:05:00 +0000 https://meredithhuffman.com/?p=2802 Recently, I’ve found that I’ve needed access to an Omeka admin dashboard without a previous admin user on the site. Installatron makes it easy to log into sites like WordPress automatically but they don’t offer this option within Omeka or other applications.

We’ve been able to figure out a way to access the site through the dashboard directly from the database. This method relies on receiving an email reset to confirm the password, but what happens when you don’t receive the email? Well, let me teach out!

Omeka Login

Once you’ve added the user to the Omeka database following the steps listed above, you’ll want to request a password reset.

This generates a user activation link that we’ll need to get to the password reset screen. Once you have the login email, you’ll want to move to the database in PHPMyAdmin.

PHPMyAdmin

In PHPMyAdmin, you’ll want to navigate to the users table. We’ll need to get the user ID of thecurrent user you just requested the password reset for.

In this case, it’s user ID 1, but it may be different for your install.

 

Next, navigate to the users_activations table. This table holds all the active Password resets for each user.

You’ll want to grab the text in the URL box next to the corresponding user_ID we got from the users table. Make sure you’re looking at the user_id section on this table as the id might be the same.

 

In the Browser

After you have that URL snippet, you’ll want to move back into the browser. We’ll need to craft out the URL from the Omeka site. You’ll go to the admin login, in this case, mine is currently at https://reclaimtest.meredithhuffman.com/admin. Next you’ll want to add the code /users/activate/u. This will create part of the password reset link. Finally, add the URL box we got from the users_activations table. So the full URL should look like this: https://reclaimtest.meredithhuffman.com/admin/users/activate/u/1140c618248acc34c9bdb924eafae99b62622b80.

Then load the page and you should see the password reset!

 

This method is super handy to get access to help troubleshoot, especially if you want to prevent back and forth between the person. I’m all for limiting any unnecessary communication.

 

]]>
Omeka S Installer Now Available https://www.reclaimhosting.com/omeka-s-installer-now-available/ https://www.reclaimhosting.com/omeka-s-installer-now-available/#respond Wed, 15 Nov 2017 09:09:19 +0000 https://www.reclaimhosting.com/?p=32282 Continue reading "Omeka S Installer Now Available"

]]>
We were very excited yesterday to see that the great team at Omeka had rolled out the official 1.0 version of Omeka S (in addition to a gorgeous new website that highlights both S and Classic versions of the software). We’ve been following the project with anticipation for quite awhile now and we know a few users have installed the software manually while it was in the alpha/beta stages. An installer has always been on our radar but we wanted to allow the Omeka team to provide a clear line of support and feedback loop for their product while it was still in beta via their forums (which continue to be a wonderful resource for support of the software with the developers very active there). With the software reaching maturity now and being publicized more widely it was time to make it easy for any Reclaim user to give it a go.

So what is Omeka S? If you’re familiar with Omeka for exhibits and one-off projects you’ll find that Omeka S is a better approach for managing multiple repositories. You have one set of code, plugins (or modules as they’re called now), and themes that are shared across the sites you create. In many ways this will remind you of WordPress Multisite versus standalone WordPress. For institutions or organizations tasked with managing more than one Omeka install this opens the door for an easier workflow. And Omeka has rebuilt their codebase from the ground up.

As of today the installer has begun rolling out to all of our servers (both shared hosting as well as institutional Domain of One’s Own systems). You’ll find installation incredibly straightforward. Simply choose the location you want to install to and fill out a few brief fields setting a name, email, and password and you’re off to the races. Here’s a quick screencast showing what that looks like:

Not ready to run it on your own domain yet? Omeka has provided a sandbox environment for you to play in so you can test the software without setting up any accounts of your own.

We could not be more pleased to continue supporting CHNM and the Omeka team as well as the larger DH community by making this available. Give it a shot and let us know what you think!

]]>
https://www.reclaimhosting.com/omeka-s-installer-now-available/feed/ 0
10,000 and 1 Reclaimers https://bavatuesdays.com/10000-and-1-reclaimers/ Tue, 08 Dec 2015 17:33:44 +0000 https://bavatuesdays.com/?p=17819 Continue reading ]]>

Crazy, last night we quietly went over 10,000 reclaimers! It’s an honor to host so many folks in higher ed who regularly share what they do!

— Reclaim Hosting (@ReclaimHosting) December 8, 2015

Last night we recorded over 10,000 users through our customer support tool Intercom. Of those, 3000 have been reported as active in their Client Area over the last month. I’m sure there is some slippage in the 10,000 number, and not all of them are still customers. But it does point to the fact that over the last two and a half years there has been an a groundswell of interest in Reclaim Hosting services beyond our wildest dreams—well, except the one involving handcuffs and Drano.

drano-o

Anyway, what Tim and I imagined as a niche interest in other schools running Domain of One’s Own pilots quickly unearthed the fact that just about everyone in educational institutions from IT to libraries to academic departments to individual courses were looking to host off-campus. And while most folks turn to the big hosts initially, it quickly becomes apparent that nobody can support students and educators using open source web applications like Reclaim Hosting. #NOBODY!!! We know what you need before you do [said while waving arms creepily, yet gracefully].

tumblr_m09yo8fx2D1r3d55uo1_500

But the aggregate is just that, and numbers can quickly become a telescopic hammer that only provide vague outlines of what’s happening. So let’s get microscopic and look at just one. Yesterday I got a question from Anna E. Kijas, Senior Digital Scholarship Librarian at Boston College Libraries, regarding some thumbnails that weren’t working on her Omeka install. Turns out the path on the server to the ImageMagick library Omeka requires was off, preventing the resizing and generation of thumbnails for images. We got that fixed, and the site was back to its original glory.

Screenshot 2015-12-08 18.08.04
Documenting Teresa

Out of curiosity I looked around Anna’s site, discovering the open access scholarly research site Documenting Teresa Carreño, dedicated to the nineteenth-century Venezuelan pianist, singer, composer, and conductor [[Teresa Carreño]]. I was learning about this world renowned pianist for the first time, and I love how each item in the collection is based on a documented performance she gave between 1862 and 1917. Here’s a random entry featuring a write-up from the The Evening World about her performance at [[Carnegie Hall]] on December 8, 1916, noting she had “maintained her power, her art, and her musicianship unimpaired.”

A perfect example of the web of sharing that I love supporting.

]]>
Setting Up S3 Storage for Omeka https://bavatuesdays.com/setting-up-s3-storage-for-omeka/ Tue, 10 Nov 2015 22:31:34 +0000 https://bavatuesdays.com/?p=17715 Continue reading ]]> Omeka continues to be a huge draw for a variety of students, faculty, and librarians using Reclaim Hosting. And the good folks at the Roy Rosenzweig Center for History and New Media have been champions of our service from the beginning, and that has made a huge difference for us. One of the issues that has come up regularly is storage for Omeka sites, which by design usually have large archives of documents, images, etc. We tend to keep our storage space for our Student and Faculty plans fairly low (2 GBs and 10 Gbs respectively) because we are trying to keep costs low, and the sales line of “unlimited” storage space for shared hosting is impractical for us. We recently introduced an Organization plan that has 100 GBs for just these instances because the need is there. That said, if you have a lot of resources you might be better off with a service like Amazon’s S3—the backup redundancy is insane and you can’t beat the price.

Screenshot 2015-11-10 23.30.05

Over 8 months ago Tim Owens figured out Omeka has the option for pushing all uploaded files to S3 built into their code. It’s just a matter of setting up an Amazon S3 bucket with the right permissions and adding the credentials to your Omeka’s config.ini file to get it running. I was intrigued by the process, but Tim had taken care of it so I knew it was theoretically possible—but never tried it. Yesterday, however, I had the opportunity to help a Reclaimer get this up and running for their Omeka install. With some help from Tim on a couple of details I missed, I got it figured out. The rest of this post will be a step-by-step for setting up S3 storage with a self-hosted Omeka site.

First and foremost you need an Amazon S3 account. S3 is cloud storage, and it is remarkably affordable if you have a large collection of files. That said, if you are Reclaiming from the corporate giants of the web, well, then…. :)  Once you have abandoned your principles and signed up for an account—it’s easy, right?—you will need to do two things in AWS.

First, you need to create a S3 bucket for your site where all the file will be uploaded. Heads up, when choosing a region outside of the U.S. (for example, Ireland is chosen in the example below) you need to define the endpoint URL in the config.ini file for Omeka. If your files are stored on Amazon servers within the US, this will not be a concern. More on that below.

Screenshot 2015-11-10 20.51.35

Once you have created your bucket you need to attach the proper bucket policy. You need to click on the “Add Bucket Policy” link at the bottom of the Properties tab for the bucket your created.

Screenshot 2015-11-10 20.52.12

The policy you probably want is read-only access for anonymous users, but there are others to choose from. In order to get the right policy (which is a snippet of code) you can go to this page here and copy the relevant code into the Bucket Policy Editor. Make sure you change the bit of code that reads examplebucket to be your bucket. in my case it would be omekatest.

Screenshot 2015-11-10 20.53.41

Once you have added that Bucket Policy the S3 bucket should be all set.

Now you need to create a user for Omeka S3 integration and grant them the proper permissions policy. You do this in the Identity & Access Management area of the Amazon AWS dashbaord, also called IAM.

Screenshot 2015-11-09 13.16.16

From the IAM area you can create a new user, once you do you will have an Access Key ID and Secret Access Key similar to those shown below.

Screenshot 2015-11-10 20.55.35Once you have the necessary keys be sure to copy and paste these somewhere, you will need them for the Omeka config.ini.

You have one last step, you need to select your appropriate user for the Omeka S3 integration.

Screenshot 2015-11-10 20.56.16

You will then need to go to the Permissions tab and attach a policy for that user.

Screenshot 2015-11-10 20.56.25

The policy you need to attach is the AmazonS3FullAccess policy.
Screenshot 2015-11-10 20.56.34 Once you do this, you are done in Amazon. You have got your bucket set up with the correct permissions, and you have the user created that will be used to authenticate into that bucket from Omeka. To finish the setup you need to go into your Omeka install and navigate to config.ini file (applications/config/config.ini)—File Manager may be the easiest way to get there in CPanel. Once there, you need to edit the file and uncomment the following section (which means removing the “;” in front of the code).

; The accessKeyId, secretAccessKey, and bucket options are all required.
; If the expiration option is set, files will be uploaded with "private"
; access, and Omeka will generate URLs that are only valid for a limited
; time. If the expiration option is missing or left commented out,
; uploaded files will always be publicly readable.
;
storage.adapter = "Omeka_Storage_Adapter_ZendS3"
storage.adapterOptions.accessKeyId = AKIAJQYON2Y66CY5HDLA
storage.adapterOptions.secretAccessKey = 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
storage.adapterOptions.bucket = omekatesting
; storage.adapterOptions.expiration = 10 ; URL expiration time (in minutes)
storage.adapterOptions.endpoint = https://s3-eu-west-1.amazonaws.com; Custom S3 endpoint (optional)

You’ll notice the AWS user Access Key and Secret key have been added, as has the bucket name. The other bit is the endpoint, which is only mandatory if you are storing files on a server outside the U.S. If so, you will need a URL like https://s3-eu-west-1.amazonaws.com as a defined endpoint so the Bucket will work. You can also set an expiration time in minutes if you need it, if not it can remain commented out.

Once you save the config.ini files with your accesskey, secret, bucketname, and endpoint (if needed) you should be all set. When you upload a file to Omeka now, it will be sent directly to this S3 bucket.

Additionally, if you already have images setup on Omeka, but would like to start using the S3 integration. You would need to copy all of your uploaded files (and the existing file structure) to that S3 Bucket. This is probably most easily done via FTP. Once you setup the config.ini file to point to S3, all existing file uploads on your site will break, so be sure to move everything ahead of time before you make S3 the default space for uploading files through Omeka.

]]>