Open Data Catalog updates
3 views
Skip to first unread message
Aaron
Sep 24, 2011, 2:52:30 AM9/24/11
to PHXdata
I did some work on the Open Data Catalog tonight -- primarily getting
al the correct dependencies in requirements.txt for easier dev
installation, and merging in some upstream commits. It's all up on
github.
I eventually got to the same error that Austin saw on my local
install. It looks like it's an email issue... maybe sendmail just
needs to be configured?
Whatever the case, if Austin or someone wants to update the server
with latest github code and look into the email issue, that'd be swell.
al the correct dependencies in requirements.txt for easier dev
installation, and merging in some upstream commits. It's all up on
github.
I eventually got to the same error that Austin saw on my local
install. It looks like it's an email issue... maybe sendmail just
needs to be configured?
Whatever the case, if Austin or someone wants to update the server
with latest github code and look into the email issue, that'd be swell.
Aaron
Sep 25, 2011, 12:50:50 AM9/25/11
to PHXdata
I have updated the server with the work I did last night, and
configured sendmail to take care of the traceback. Registration and
data submission are now functional.
There are several pieces of metadata in the submission process that
aren't configured out of the box -- update frequency, coordinate
system, data types, and data formats. This would be a good job for any
non-programmers who want to contribute -- ask me, and I'll set up up
with an admin account. These can all be added through Django's admin
interface, which lets you add database data by filling a
straightforward web form.
If you don't know what options to include, just look at what Open Data
Philly is including in their forms.
Another job for someone who's comfortable enough with html & github
(but not necessarily Python programming): find all the occurrences of
strings like "OpenDataPhilly," "Philadelphia", etc. and modify. I'm
seeing that in the registration process, confirmation email, and data
submission form. I'm sure there are occurrences elsewhere too.
Directory/project search tools are your friend.
configured sendmail to take care of the traceback. Registration and
data submission are now functional.
There are several pieces of metadata in the submission process that
aren't configured out of the box -- update frequency, coordinate
system, data types, and data formats. This would be a good job for any
non-programmers who want to contribute -- ask me, and I'll set up up
with an admin account. These can all be added through Django's admin
interface, which lets you add database data by filling a
straightforward web form.
If you don't know what options to include, just look at what Open Data
Philly is including in their forms.
Another job for someone who's comfortable enough with html & github
(but not necessarily Python programming): find all the occurrences of
strings like "OpenDataPhilly," "Philadelphia", etc. and modify. I'm
seeing that in the registration process, confirmation email, and data
submission form. I'm sure there are occurrences elsewhere too.
Directory/project search tools are your friend.
joeydi
Sep 25, 2011, 1:02:59 AM9/25/11
to PHXdata
Aaron -
Great work. Just got my account set up. I am working on getting a
local dev setup going. I made some formatting changes to the README,
and will any any notes I think are helpful during installation.
Looking into populating those defaults now.
Great work. Just got my account set up. I am working on getting a
local dev setup going. I made some formatting changes to the README,
and will any any notes I think are helpful during installation.
Looking into populating those defaults now.
joeydi
Sep 25, 2011, 1:07:41 AM9/25/11
to PHXdata
Set me up with an admin account and I'll populate some coordinates
systems, etc.
systems, etc.
joeydi
Sep 25, 2011, 1:17:42 AM9/25/11
to PHXdata
You should also enable Issues on the github repo so that we can start
collecting all the ideas/task/etc.
collecting all the ideas/task/etc.
Aaron
Sep 25, 2011, 1:49:24 AM9/25/11
to PHXdata
I enabled Issues in the github repo.
Your existing account now has superuser permissions -- log in at
catalog.phxdata.org/_admin_/
Lastly, be sure to pull from github before changing too much. I just
pushed some changes to styling and such, so it doesn't look quite as
broken as before.
Your existing account now has superuser permissions -- log in at
catalog.phxdata.org/_admin_/
Lastly, be sure to pull from github before changing too much. I just
pushed some changes to styling and such, so it doesn't look quite as
broken as before.
Michael Alexander
Sep 25, 2011, 2:02:13 AM9/25/11
to phx...@googlegroups.com
About "OpenDataPhilly," "Philadelphia", etc, what should those occurrences be changed to?
> --
> You received this message because you are subscribed to the Google
> Groups "PHXdata" group.
> To post to this group, send email to phx...@googlegroups.com
> To unsubscribe from this group, send email to
> phxdata+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/phxdata
> You received this message because you are subscribed to the Google
> Groups "PHXdata" group.
> To post to this group, send email to phx...@googlegroups.com
> To unsubscribe from this group, send email to
> phxdata+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/phxdata
Longcreative
Sep 25, 2011, 2:45:26 AM9/25/11
to PHXdata
Let me know what I can do. Don't want to replicate efforts....so I
will let you guys drive. I'm new to Git...but I think I have
everything set up right.
Do we need some data sets to test things out?
will let you guys drive. I'm new to Git...but I think I have
everything set up right.
Do we need some data sets to test things out?
Aaron
Sep 25, 2011, 4:41:45 PM9/25/11
to PHXdata
To be honest, I'm not sure. I just called the site "Phoenix Data
Catalog" as it corresponds with the URL... but no one has come up with
an official name, copy or anything. That's not my area of expertise.
If no one takes on that role within the next couple of days, just wing
it. "Phoenix Data Catalog" and "Phoenix" should work well enough as
substitutes for those two, for now. I'm not sure about branding this a
"Phoenix" resource though, as I think it's really intended for the
whole state.
On Sep 24, 11:02 pm, Michael Alexander <mxan...@gmail.com> wrote:
> About "OpenDataPhilly," "Philadelphia", etc, what should those occurrences
> be changed to?
Catalog" as it corresponds with the URL... but no one has come up with
an official name, copy or anything. That's not my area of expertise.
If no one takes on that role within the next couple of days, just wing
it. "Phoenix Data Catalog" and "Phoenix" should work well enough as
substitutes for those two, for now. I'm not sure about branding this a
"Phoenix" resource though, as I think it's really intended for the
whole state.
On Sep 24, 11:02 pm, Michael Alexander <mxan...@gmail.com> wrote:
> About "OpenDataPhilly," "Philadelphia", etc, what should those occurrences
> be changed to?
Aaron
Sep 25, 2011, 4:43:43 PM9/25/11
to PHXdata
Data sets would be great, both to test out the submission process, and
to give the site some useful content.
I'm still not sure how the approval process works for data
submissions.
to give the site some useful content.
I'm still not sure how the approval process works for data
submissions.
Michael Alexander
Sep 25, 2011, 5:29:14 PM9/25/11
to phx...@googlegroups.com
Are we distinguishing the Phoenix Data Catalog service from the PHXdata team?
This is my initial contribution, so I don't want to step on toes.
Mark Ng
Sep 25, 2011, 5:33:47 PM9/25/11
to phx...@googlegroups.com
the PHXData team is whoever is prepared to step up and do something at
that moment in time. :) If that's you at that particular moment in
time, you're part of it.
that moment in time. :) If that's you at that particular moment in
time, you're part of it.
People stepping on each others toes because lots of people are
contributing is a good problem to have, and when we have it, we'll
worry about it then. For the moment, step away !
Mark
Nick Martin
Sep 25, 2011, 9:37:29 PM9/25/11
to phx...@googlegroups.com
It sounds like catalog is a project of PHXdata. They are one in the same. So in terms of what to fill in, unless there is some objection, we should probably replace instances of "OpenDataPhilly" with "PHXdata."
Nick
Sent from my mobile device
Austin Godber
Sep 25, 2011, 10:14:33 PM9/25/11
to phx...@googlegroups.com
I have sent a pull request with the Phillys changed to Phoenix. And where they use OpenDataPhilly, I have said "the PHXdata Catalog". If anyone feels strongly, I'd change it to something else.
Good job everyone for thinking about this again. I think I have gone through the overhead of getting setup (mostly) for working on this. I might be able to help a bit more. BTW, I will probably not be able to resist cleaning the python code up to adhere to PEP8 (http://www.python.org/dev/peps/pep-0008/), retab with spaces and remove whitespace. I hope no-one minds.
Austin
Michael Alexander
Sep 25, 2011, 10:30:54 PM9/25/11
to phx...@googlegroups.com
Coincidentally, I submitted a pull request before Nick and Austin's emails.
I replaced "OpenDataPhilly" with "Phoenix Data Catalog" and "OpenDataPhilly Crew" with "PHXdata Crew."
Feel free to ignore my replacements since Nick's suggestions seem reasonable, otherwise, I'm willing to push corrections.
Let me know.
Thanks,
M
Austin Godber
Sep 25, 2011, 10:32:16 PM9/25/11
to phx...@googlegroups.com
Haha, I just saw that, I closed my req since yours was far more thorough.
Austin
Aaron
Sep 25, 2011, 11:29:59 PM9/25/11
to PHXdata
Don't mind at all; ugly code is unpleasant. Clean away.
On Sep 25, 7:14 pm, Austin Godber <god...@gmail.com> wrote:
> I have sent a pull request with the Phillys changed to Phoenix. And where
> they use OpenDataPhilly, I have said "the PHXdata Catalog". If anyone feels
> strongly, I'd change it to something else.
>
> Good job everyone for thinking about this again. I think I have gone
> through the overhead of getting setup (mostly) for working on this. I might
> be able to help a bit more. BTW, I will probably not be able to resist
> cleaning the python code up to adhere to PEP8 (http://www.python.org/dev/peps/pep-0008/), retab with spaces and remove
> whitespace. I hope no-one minds.
>
> Austin
>
On Sep 25, 7:14 pm, Austin Godber <god...@gmail.com> wrote:
> I have sent a pull request with the Phillys changed to Phoenix. And where
> they use OpenDataPhilly, I have said "the PHXdata Catalog". If anyone feels
> strongly, I'd change it to something else.
>
> Good job everyone for thinking about this again. I think I have gone
> through the overhead of getting setup (mostly) for working on this. I might
> be able to help a bit more. BTW, I will probably not be able to resist
> cleaning the python code up to adhere to PEP8 (http://www.python.org/dev/peps/pep-0008/), retab with spaces and remove
> whitespace. I hope no-one minds.
>
> Austin
>
> On Sun, Sep 25, 2011 at 6:37 PM, Nick Martin <emailnickmar...@gmail.com>wrote:
>
>
>
>
>
>
>
> > It sounds like catalog is a project of PHXdata. They are one in the same.
> > So in terms of what to fill in, unless there is some objection, we should
> > probably replace instances of "OpenDataPhilly" with "PHXdata."
>
> > Nick
>
> > Sent from my mobile device
>
>
>
>
>
>
>
> > It sounds like catalog is a project of PHXdata. They are one in the same.
> > So in terms of what to fill in, unless there is some objection, we should
> > probably replace instances of "OpenDataPhilly" with "PHXdata."
>
> > Nick
>
> > Sent from my mobile device
> > On Sep 25, 2011 2:33 PM, "Mark Ng" <m...@markng.me.uk> wrote:
> > > the PHXData team is whoever is prepared to step up and do something at
> > > that moment in time. :) If that's you at that particular moment in
> > > time, you're part of it.
>
> > > People stepping on each others toes because lots of people are
> > > contributing is a good problem to have, and when we have it, we'll
> > > worry about it then. For the moment, step away !
>
> > > Mark
>
> > > the PHXData team is whoever is prepared to step up and do something at
> > > that moment in time. :) If that's you at that particular moment in
> > > time, you're part of it.
>
> > > People stepping on each others toes because lots of people are
> > > contributing is a good problem to have, and when we have it, we'll
> > > worry about it then. For the moment, step away !
>
> > > Mark
>
> > > On 25 September 2011 14:29, Michael Alexander <mxan...@gmail.com> wrote:
> > >> Are we distinguishing the Phoenix Data Catalog service from the PHXdata
> > >> team?
> > >> This is my initial contribution, so I don't want to step on toes.
>
> > >> Are we distinguishing the Phoenix Data Catalog service from the PHXdata
> > >> team?
> > >> This is my initial contribution, so I don't want to step on toes.
>
Aaron
Sep 25, 2011, 11:35:48 PM9/25/11
to PHXdata
A bit late to mention this, but ideally all such mentions would be
replaced by constants defined in the settings -- so we can easily
switch if we change our mind, and others can more easily adopt this if
they chose to fork from us.
I'll look over pull requests and update the site tomorrow.
On Sep 25, 7:32 pm, Austin Godber <god...@gmail.com> wrote:
> Haha, I just saw that, I closed my req since yours was far more thorough.
>
> Austin
>
replaced by constants defined in the settings -- so we can easily
switch if we change our mind, and others can more easily adopt this if
they chose to fork from us.
I'll look over pull requests and update the site tomorrow.
On Sep 25, 7:32 pm, Austin Godber <god...@gmail.com> wrote:
> Haha, I just saw that, I closed my req since yours was far more thorough.
>
> Austin
>
> On Sun, Sep 25, 2011 at 7:30 PM, Michael Alexander <mxan...@gmail.com>wrote:
>
>
>
>
>
>
>
> > Coincidentally, I submitted a pull request before Nick and Austin's
> > emails.
> > I replaced "OpenDataPhilly" with "Phoenix Data Catalog" and "OpenDataPhilly
> > Crew" with "PHXdata Crew."
> > Feel free to ignore my replacements since Nick's suggestions seem
> > reasonable, otherwise, I'm willing to push corrections.
> > Let me know.
>
> > Thanks,
>
> > M
>
> > On Sun, Sep 25, 2011 at 7:14 PM, Austin Godber <god...@gmail.com> wrote:
>
> >> I have sent a pull request with the Phillys changed to Phoenix. And where
> >> they use OpenDataPhilly, I have said "the PHXdata Catalog". If anyone feels
> >> strongly, I'd change it to something else.
>
> >> Good job everyone for thinking about this again. I think I have gone
> >> through the overhead of getting setup (mostly) for working on this. I might
> >> be able to help a bit more. BTW, I will probably not be able to resist
> >> cleaning the python code up to adhere to PEP8 (
> >>http://www.python.org/dev/peps/pep-0008/), retab with spaces and remove
> >> whitespace. I hope no-one minds.
>
> >> Austin
>
>
>
>
>
>
>
>
> > Coincidentally, I submitted a pull request before Nick and Austin's
> > emails.
> > I replaced "OpenDataPhilly" with "Phoenix Data Catalog" and "OpenDataPhilly
> > Crew" with "PHXdata Crew."
> > Feel free to ignore my replacements since Nick's suggestions seem
> > reasonable, otherwise, I'm willing to push corrections.
> > Let me know.
>
> > Thanks,
>
> > M
>
> > On Sun, Sep 25, 2011 at 7:14 PM, Austin Godber <god...@gmail.com> wrote:
>
> >> I have sent a pull request with the Phillys changed to Phoenix. And where
> >> they use OpenDataPhilly, I have said "the PHXdata Catalog". If anyone feels
> >> strongly, I'd change it to something else.
>
> >> Good job everyone for thinking about this again. I think I have gone
> >> through the overhead of getting setup (mostly) for working on this. I might
> >> be able to help a bit more. BTW, I will probably not be able to resist
> >> cleaning the python code up to adhere to PEP8 (
> >>http://www.python.org/dev/peps/pep-0008/), retab with spaces and remove
> >> whitespace. I hope no-one minds.
>
> >> Austin
>
> >> On Sun, Sep 25, 2011 at 6:37 PM, Nick Martin <emailnickmar...@gmail.com>wrote:
>
> >>> It sounds like catalog is a project of PHXdata. They are one in the same.
> >>> So in terms of what to fill in, unless there is some objection, we should
> >>> probably replace instances of "OpenDataPhilly" with "PHXdata."
>
> >>> Nick
>
> >>> Sent from my mobile device
>
> >>> It sounds like catalog is a project of PHXdata. They are one in the same.
> >>> So in terms of what to fill in, unless there is some objection, we should
> >>> probably replace instances of "OpenDataPhilly" with "PHXdata."
>
> >>> Nick
>
> >>> Sent from my mobile device
> >>> On Sep 25, 2011 2:33 PM, "Mark Ng" <m...@markng.me.uk> wrote:
> >>> > the PHXData team is whoever is prepared to step up and do something at
> >>> > that moment in time. :) If that's you at that particular moment in
> >>> > time, you're part of it.
>
> >>> > People stepping on each others toes because lots of people are
> >>> > contributing is a good problem to have, and when we have it, we'll
> >>> > worry about it then. For the moment, step away !
>
> >>> > Mark
>
> >>> > On 25 September 2011 14:29, Michael Alexander <mxan...@gmail.com>
> >>> > the PHXData team is whoever is prepared to step up and do something at
> >>> > that moment in time. :) If that's you at that particular moment in
> >>> > time, you're part of it.
>
> >>> > People stepping on each others toes because lots of people are
> >>> > contributing is a good problem to have, and when we have it, we'll
> >>> > worry about it then. For the moment, step away !
>
> >>> > Mark
>
> >>> wrote:
> >>> >> Are we distinguishing the Phoenix Data Catalog service from the
> >>> PHXdata
> >>> >> team?
> >>> >> This is my initial contribution, so I don't want to step on toes.
>
> >>> >> Are we distinguishing the Phoenix Data Catalog service from the
> >>> PHXdata
> >>> >> team?
> >>> >> This is my initial contribution, so I don't want to step on toes.
>
Longcreative
Sep 26, 2011, 2:04:34 AM9/26/11
to PHXdata
I redid some stuff on the PhxData home page and sent a pull
request....if I did it right? Who would do that?
On Sep 25, 2:33 pm, Mark Ng <m...@markng.me.uk> wrote:
> the PHXData team is whoever is prepared to step up and do something at
> that moment in time. :) If that's you at that particular moment in
> time, you're part of it.
>
> People stepping on each others toes because lots of people are
> contributing is a good problem to have, and when we have it, we'll
> worry about it then. For the moment, step away !
>
> Mark
>
request....if I did it right? Who would do that?
On Sep 25, 2:33 pm, Mark Ng <m...@markng.me.uk> wrote:
> the PHXData team is whoever is prepared to step up and do something at
> that moment in time. :) If that's you at that particular moment in
> time, you're part of it.
>
> People stepping on each others toes because lots of people are
> contributing is a good problem to have, and when we have it, we'll
> worry about it then. For the moment, step away !
>
> Mark
>
> On 25 September 2011 14:29, Michael Alexander <mxan...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Are we distinguishing the Phoenix Data Catalog service from the PHXdata
> > team?
> > This is my initial contribution, so I don't want to step on toes.
>
>
>
>
>
>
>
>
> > Are we distinguishing the Phoenix Data Catalog service from the PHXdata
> > team?
> > This is my initial contribution, so I don't want to step on toes.
>
Austin Godber
Sep 26, 2011, 9:57:56 AM9/26/11
to phx...@googlegroups.com
Has anyone had luck actually submitting data? I haven't.
https://github.com/phxdata/Open-Data-Catalog/issues/4
I am not sure when I will pick this up again, but I will eventually look at it.
I am not sure when I will pick this up again, but I will eventually look at it.
Austin
Aaron
Sep 26, 2011, 1:33:26 PM9/26/11
to PHXdata
I just merged in the two open pull requests and updated the site.
Thanks Joe & Austin.
Andrew, I didn't see an open pull request from you. Github has some
good docs on how to fork & send pull requests, if you haven't seen
them yet:
http://help.github.com/fork-a-repo/
http://help.github.com/send-pull-requests/
Thanks Joe & Austin.
Andrew, I didn't see an open pull request from you. Github has some
good docs on how to fork & send pull requests, if you haven't seen
them yet:
http://help.github.com/fork-a-repo/
http://help.github.com/send-pull-requests/
Longcreative
Sep 26, 2011, 1:53:43 PM9/26/11
to PHXdata
I was working on https://github.com/phxdata/PHXdata-Website
not the catalog. Do you control that? Or Brian?
a.
not the catalog. Do you control that? Or Brian?
a.
Aaron
Sep 26, 2011, 2:33:27 PM9/26/11
to PHXdata
Ah, didn't look there.
Any PHXdata "owner" can merge that in -- currently that's Mark Ng,
Marc Chung, Brian Shaler, and me.
I'll try to get that done tonight or tomorrow, if someone else doesn't
get to it first.
On Sep 26, 10:53 am, Longcreative <longcreat...@gmail.com> wrote:
> I was working onhttps://github.com/phxdata/PHXdata-Website
> > them yet:http://help.github.com/fork-a-repo/http://help.github.com/send-pull-r...
Any PHXdata "owner" can merge that in -- currently that's Mark Ng,
Marc Chung, Brian Shaler, and me.
I'll try to get that done tonight or tomorrow, if someone else doesn't
get to it first.
On Sep 26, 10:53 am, Longcreative <longcreat...@gmail.com> wrote:
> I was working onhttps://github.com/phxdata/PHXdata-Website
Aaron
Sep 27, 2011, 1:14:04 AM9/27/11
to PHXdata
I merged in your changes. I don't think I have access to the server
it's running on however, so I can't update the live site.
We should probably move this to github sites as Mark Ng suggested...
> I was working onhttps://github.com/phxdata/PHXdata-Website
> > them yet:http://help.github.com/fork-a-repo/http://help.github.com/send-pull-r...
it's running on however, so I can't update the live site.
We should probably move this to github sites as Mark Ng suggested...
> I was working onhttps://github.com/phxdata/PHXdata-Website
Reply all
Reply to author
Forward
0 new messages