-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: workshops/models.py: Add Host and EventHost models #120
Conversation
To distinguish between the Site (a physical location, e.g. TGAG, the Genome Analysis Centre, Norwich Research Park, Colney, Norwich, Norfolk, United Kingdom, 52.621699 N, 1.21888 E) and the Host (possibly a diffuse entity, e.g. ELIXIR, the European life-sciences Infrastructure for biological Information). A diffuse host can have many sites, and a particular workshop can have many collaborating hosts. The many-to-many relationship (one host can support several events, and one event may have several hosts) is not layed out explicitly in our charter, but [1] has: *Hosting* a workshop means providing space for it, supporting travel costs for instructors (if applicable), etc. and its conceivable that one host could provide space while others could fund instructor travel, etc. I've added the free-form EventHost.notes to keep track of this, and I expect it will have values like "providing the site", "funding travel for instructor Alice Bobsdaughter", "providing coffee and snacks for the first day of the event", etc. If a single host provides for the whole event, I'd just leave this field blank. [1]: https://github.com/swcarpentry/board/blob/master/membership.md#terminology
I think
(with a similar |
|
d4134f9
to
af12dcd
Compare
On Tue, Jan 06, 2015 at 06:03:18PM -0800, Greg Wilson wrote:
You're never going to have multiple sponsors for a workshop? I think
Works for me.
Done in #126. |
I don't think we're going to incorporate this any time soon - permission to close? |
On Wed, May 27, 2015 at 10:39:09AM -0700, Greg Wilson wrote:
@pbanaszkiewicz added this to v0.4 yesterday. |
I've scheduled it for discussion in v0.4 window, but I didn't go into the code. |
Close as stale? |
Can we discuss this after we release v0.3? |
On Mon, Jun 01, 2015 at 10:52:09AM -0700, Greg Wilson wrote:
I think this is still a good idea. If it doesn't get into v0.4 as |
We can address some of the modeling issues before I get around to
|
I understand that this makes sense in DB terms; I doubt the admins using
the system will ever input the information (and will regard the
complication of the common case as unwelcome).
|
On Mon, Jun 01, 2015 at 11:09:09AM -0700, Greg Wilson wrote:
Which information? Just the distinction between sites and hosts? How if the Partner is a distributed collaboration, no more than one third in which case we'd need to distinguish between that parter's (Host's) |
On Fri, Jun 12, 2015 at 04:37:21AM -0700, Piotr Banaszkiewicz wrote:
Hmm, so “keep the current conflation between Sites and Hosts, but add
After the migration, I expect Host data to be pretty stable and grow This still doesn't address the “do we want to track multiple |
This is a quickfix for carpentries#353 before we implement proper distinction between Host and Site (see carpentries#120).
Ref #5 (comment) |
Closing since we opted for #440 implementation instead. |
To distinguish between the Site (a physical location, e.g. TGAG, the
Genome Analysis Centre, Norwich Research Park, Colney, Norwich,
Norfolk, United Kingdom, 52.621699 N, 1.21888 E) and the Host
(possibly a diffuse entity, e.g. ELIXIR, the European life-sciences
Infrastructure for biological Information). A diffuse host can have
many sites, and a particular workshop can have many collaborating
hosts. The many-to-many relationship (one host can support several
events, and one event may have several hosts) is not layed out
explicitly in our charter, but we have:
and its conceivable that one host could provide space while others
could fund instructor travel, etc. I've added the free-form
EventHost.notes to keep track of this, and I expect it will have
values like "providing the site", "funding travel for instructor Alice
Bobsdaughter", "providing coffee and snacks for the first day of the
event", etc. If a single host provides for the whole event, I'd just
leave this field blank.
This pull request is currently a work-in-progress while we work out
the models, after which I'll go through and fill in the migrations,
view changes, etc. I'll remove the WIP note in the summary once I
think it's ready for merging.
Fixes #5 and #6.