search

codeforamerica / ohana-api

The open source API directory of community social services.
http://ohana-api-demo.herokuapp.com/api
BSD 3-Clause "New" or "Revised" License
185 stars 344 forks source link

Help with using the Admin Interface #260

Closed devinbalkind closed 9 years ago

devinbalkind commented 9 years ago

Thanks to the awesome work of @volkanunsal NYC:Prepared has a working deployment of Ohana.

Now comes the challenge of managing administering this system.

Is there a user guide out there for how to use Ohana once it's been deployed? I'd be happy to contribute what I discover to such a project.

Now comes a usage question: how do I change the organization associated with a location and service?

Currently our search interface is here: https://nyc-prepared-search.herokuapp.com/ And our admin is here: https://nyc-prepared.herokuapp.com/

monfresh commented 9 years ago

That's great! Note that I'm making changes just about every day, and adding new things to the admin interface, so make sure to pull the latest code.

As for a user guide, there isn't one at the moment. If there are specific questions you have, or think something is confusing, let me know and I'll clear things up.

As for changing the organization associated with a location, I'm assuming you mean that Location A belongs to Organization B, but now you want to make it belong to Organization C. If that's what you mean, then that's not allowed currently for security reasons. It's possible to allow that change for Super Admins, but my first question is, "Why was Location A associated with the wrong organization in the first place?"

How many locations do you have that are associated with the wrong organization? If it's more than one, I would clean up your original data and import it back. The original data is also assumed to be compliant with the OpenReferral spec. Otherwise, you end up with a search interface that displays invalid and incomplete data.

There have been lots of API changes over the past few weeks, some of which I see your deployment hasn't picked up yet, such as the number_type for a phone number, which is now required but is missing from your data.

If you only have one location (or however many you feel like recreating) with the wrong organization, the way you would fix this currently is by following these steps:

  1. Sign in to the admin interface
  2. Click the "Add new location" button
  3. Select the correct Organization at the top of the form
  4. Fill out the rest of the details for this location, and click the "Create location" button
  5. Click the link for your new location
  6. Add Contacts and Services to it
  7. Go to the original "bad" location and delete it.
devinbalkind commented 9 years ago

The location - organization associatioin was wrong because of the data we imported into the system.

I'm only going through this data now but it's clear to me that I'll need to change this for a number of services and locations.

I think super admins should have this ability. Bad import data is probably the most common reason for this type of error, but programs and locations do change, particularly in disaster relief where program funding changes and locations and services do move between groups.

Thanks for the instructions. I'll add them to the user guide I'm creating for my deployment and will share it with the group when it becomes interesting.

monfresh commented 9 years ago

I just created this Wiki article about the admin interface: https://github.com/codeforamerica/ohana-api/wiki/Admin-interface-basics I hope it helps. Can I close this issue?

monfresh commented 9 years ago

I think this has been resolved, so I'm closing it. Feel free to reopen if that's not the case.

devinbalkind commented 9 years ago

Yes I think it has.

Thanks so much.

On Sat, Nov 15, 2014 at 12:04 PM, Moncef Belyamani <notifications@github.com

wrote:

I think this has been resolved, so I'm closing it. Feel free to reopen if that's not the case.

— Reply to this email directly or view it on GitHub https://github.com/codeforamerica/ohana-api/issues/260#issuecomment-63179430 .

Devin Balkind Founder & Director, Sarapis http://sarapis.org Lead Coordinator, NYC:Prepared http://nycprepared.org 134 Spring St, Suite 302 New York, NY, 10012 m.917.748.1048 devin@sarapis.org