Skip to content
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

Set up data exchange points with SCALE's Drupal setup #9

Open
GoogleCodeExporter opened this issue Mar 17, 2015 · 4 comments
Open

Set up data exchange points with SCALE's Drupal setup #9

GoogleCodeExporter opened this issue Mar 17, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

At some point we may need to share data between scalereg and Drupal on the
SCALE server. We need to figure out what needs to be shared, when, and in
what format. Access control may also be an issue.

Original issue reported on code.google.com by [email protected] on 24 Jun 2009 at 8:54

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 24 Jun 2009 at 8:55

  • Changed state: Assigned

@GoogleCodeExporter
Copy link
Author

The priority probably increases once we've implemented the CFP system in 
Django. 
Shyam and Matt will likely want to be able to post the conference data to the
website, without duplicating it.

Original comment by [email protected] on 9 Aug 2009 at 11:02

@GoogleCodeExporter
Copy link
Author

With the SCALE cfp ending on 12/24 we will quickly find a need to make this 
data 
available via the front end website.  The currently proposed/discussed method 
is for 
simple_cfp to provide an RSS or ATOM feed containing speaker information which 
drupal can consume on a schedule

Original comment by [email protected] on 23 Dec 2009 at 5:18

@GoogleCodeExporter
Copy link
Author

RSS based fees were created for approved speakers and presentations.  We can 
probably
close this issue out.

Original comment by [email protected] on 17 Jan 2010 at 12:11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant