Rails Project: Hidden Mickey Pin Binder

Posted by Amanda Murphy on July 17, 2019

Hey there!

I just completed my first draft of my Rails project, and while I’ll talk a little bit about my first Ruby on Rails web application, I also want to share a couple of the challenges I encountered while building this project.

My Rails Application

I wasn’t certain what direction I wanted to go with for my Rails application. I considered rebuilding my Sinatra project, because I was really proud of it, but ultimately decided to create a new project inspired by my love of Disney.

I always loved Disney movies, but in 2014, I went to Walt Disney World for the first time. That was the beginning of my love for Disney World.

Identifying an Area of Opportunity

One of my favorite things to do in Disney World is collect pins. For those of you who aren’t familiar with pin trading, the Disney parks sell collectible pins that you can purchase. But there’s also a second kind of pin you can’t buy: Hidden Mickey pins. Hidden Mickey pins have small silver Mickey Mouse silhouettes on them and are released in series to the cast members who work at Disney. The cast members wear their pins on lanyards or pin belts, and are required to trade with any guest who requests a pin trade.

A photo of my pin lanyard from my first trip to Disney World in 2014.

It usually starts with seeing a pin a cast member is wearing, and trading for that specific pin. On the back of each pin are two numbers: the pin’s number in the series / the number of pins in the series. So then you search to complete the set, either by finding similar looking pins–My husband collected a set that were all shaped like neckties; or you take a photo of a paper copy of the pin release that is in a binder at a Pin Trading Station that shows what pins are in the series–we’ve found this elusive binder once in about ten visits.

So yes, each year, Disneyland and Walt Disney World release several series each quarter, and there are no sites that have all Hidden Mickey Pin series in an official capacity available online.

I’m no user experience expert, but it seemed like a ripe area of opportunity.

Learning More

Part of our Pin Collection

I did a little Googling and found there was a Pin Trading Database. It exists, but there were a lot of problems I could identify. I had my husband take a look at it, and bless his UX Designer brain–he flinched. I asked if he could come up with a design for an improved site, and he began a diatribe about site mapping, dead pages, information architecture, and how it was antithetical to UX as a field to design something just because he thought it would work. I didn’t understand most of what he was saying, but he agreed that we could do some user testing in the future to see what exactly wasn’t working on the page, and how to improve it.

He knows what he’s talking about, and I’m just here to build things that will lead Disney to either buy a product from me, or better yet, hire me.

I identified a few glaring issues with the site to inform how I built my site.

  • It included all pins. There are a set number of Hidden Mickey pins, but there are likely an unknowable number of official Disney pins (the kind that are sold in the Parks.)
  • Users created their own pins. Meaning there are likely thousands of duplicate pins in the database.
  • Identification numbers were based on the database ID numbers, not an officially assigned number.
  • The pin photographs were bad.
  • The site looks bad.
  • The site shows a list of all users by username. (That’s not the worst as far as security issues are concerned, but it makes me cringe.)

I decided I wanted to create my site with the following in mind:

  • I wanted to narrow the pins in my database down to just Hidden Mickey pins.
  • I want to input all pin information into the database (in the future) and have users add those pins to their collection, rather than create a new pin every time.
  • I wanted to find an easy way to identify each unique pin.

I did a little more Googling and could not find a comprehensive list of the Hidden Mickey series or their information. I found a few years online from various sites and saved them for future use.

And then I did something that was out of character for me: I reached out to a stranger on social media. I had been following a Disney cast member for a year on social media, and so I messaged the cast member and asked if there was any place I might be able to find information on all of the Hidden Mickey series. The person responded quickly and explained that Disney used to have a site for it, as well as Pin checklists, but had done away with both. The person said they might have to dig around, but he/she could potentially send me a copy of the lists they had. (Ya know, since it used to be public information.)

I was a little disappointed to find out my idea wasn’t new–Disney had the same idea before me, and had determined it wasn’t worth the work it took to support the website. (In the words of Mickey Mouse, “Awwww shucks!”) But I went ahead and decided to proceed with the project anyway.

*I haven’t received the information from the cast member yet, but I’m still crossing my fingers. *

Making the Thing

I’ll be honest. Sinatra was really easy for me. I completed all of the project requirements two days after I started. Rails was a different story.

Using PostgreSQL for the First Time

After talking to my project coach about what I had planned, he suggested using PostgreSQL so that I could share my Rails project on Heroku once it was complete. That sounded great to me, because it was someting I wanted to do with my Sinatra project as well.

So I’m typing and building things and creating migrations, but then the migrations…won’t migrate. I ran rake db:migrate and the terminal slings back:

rake aborted!
PG::ConnectionBad: could not connect to server: No such file or directory
    Is the server running locally and accepting
    connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

Okay, say what now? I open up my PostgreSQL app, and initialize the server. It’s still not working. So I keep Googling, and I find the instructions on the Postgres.app site very helpful. But I was still having issues, and receiving this error:

ActiveRecord::NoDatabaseError: FATAL: database “hiddenmickey_development” does not exist

So I threw that error into Google and found this Stack Overflow page.

The Stack Overflow response suggested running this in the command line: bundle exec rake db:create. So I ran that, followed by rake db:migrate and voila! I had a database.

My Instance isn’t Saving

I was hoping that database issue was the only bump in the road, but I was wrong.

I too experienced the classic, “My instance isn’t saving” issue.

I had a similar issue in my Sinatra project (I tried to name an instance “request” which is a word we don’t touch when building the things.) so I was convinced it was due to naming my instance “pin.” (My User model was working just fine.) I went through and changed everything named “pin.” It was a total mess, and did not change anything.

I threw up my hands and asked the Slack Gods (the more experienced Flatiron School students) for any advice. One of the students suggested I throw a pry in the create method and run @pin.errors. I don’t know why I hadn’t thought of that, but I had not. I realized my pin instance would not save because I was not assigning a User to @pin in my create method, and I also had neglected to add user_id as an attribute on my Pins table. (For anyone not tracking: when you use a belongs_to relationship in your Rails models, it requires that you assign what the instance belongs to in your create method and your table.)

This Table is Droppin’

Call me inexperienced, because this is embarrassing. Once I had resolved my create issue with my Pin instance, I realized I had another issue: all of the users I had created had vanished (or they weren’t saving.) It took me a second to realize why.

When I’m working on a project with no real data, I don’t like to add a million migrations to alter a table. I have been running rake db:drop, making changes, and then running rake db:migrate–all this time, not realizing that when you drop the table…the information in your table goes bye bye.

To save myself time, I created seeds for the first time! That way, every time I dropped the table, I could repopulate the new table with the same information.

The Best Resource

After my instance wouldn’t save in the create method, I started watching these walkthrough videos by Flatiron School Technical Coach, Jenn Hansen. I can’t emphasize how helpful these videos were–if you’re just starting your Rails project, definitely watch them. (It’s a lot of information, but I watch them on 1.5x speed and still catch it all.) You can find her Rails Walkthrough playlist here.

What Next?

I have a few other topics I learned while working on this project, that I’m hoping to write future (more technical) blog posts about including: Omniauth, using enums, and possible nested forms.

As far as my Rails application goes, I would like to:

  • Implement Bootstrap or custom CSS styling
  • Change the new pin form so that if you select one option (perhaps what series the pin belongs to) the form would update to reflect pin information from pins only in that series. Example: If you have a pin with Aurora on it, you could select Aurora as the pin’s subject, and the series select list would reflect only series that contained Aurora in them, as well as a photo of the pin you were adding to confirm you were adding the correct pin.
  • Add all existing pin and series information I have into the database
  • Add a button at the bottom of a pin show page that you could click and it would instantly add that pin to your collection.
  • Add trading and selling functionality.
  • Use Devise for sign up and log in.

I am really happy to have completed this project, and look forward to adding JavaScript to it for my next project. (Hopefully I’ll have some help from my resident UX student to improve the site as well.)

You can view the code here, and the demo here.