joindin / callingallpapers-api Goto Github PK

Users shall be able to set different notification periods for differrnt CfPs

Like

• CoC (available? If so: Link)
• What expenses are covered (or partly covered)?
  • transport
  • accommodation
  • event-entrance
• What other perks are there? (Sightseeing tour, speaker-dinner, partner covered...)

Currently the API just lists available CfPs.

There should also be an endpoint where one can search for CfPs matching certain criteria like within a range around a geolocation, starting or ending at a certain date or having a certain tag.

Currently the URI of the event is used to identify unique events over different sources. Currently the event-URI is hashed "as-is". But as the URI might or might not have a slash at the end there are some events available twice. That's not necessarily what we want.

Therefore the Event-URI needs to be sanitized before adding to the API

users shall be able to search based on their geolocation and only retrieve CfPs from within a certain radius, only within certain countries or continents and only within certain timezones

I noticed a few days ago that many of the dates from papercall CFPs are showing up as 12/31/1969 on the site. It also seems from looking at the data that locations are not being parsed correctly.

I'm happy to help with this, but wanted to file the issue first in case it's a known problem.

Currently the database has to be created by hand when starting from scratch.

Can we ease that by adding something to create the database if it doesn't exist?

Hi There,

I tried to request an API key but looks like the email has been deactivated. Are there other ways to request a key?

Best,

Users can log in using third-party auth backends like twitter or github.

Logged in users can set notification preferences like email-address and the time before the end of a CfP they want to be notified.

Instead of taking the description from the CfP-Aggregator-Site we should take the information from the Meta-Data of the event (or the CfP?) website

Currently all CfPs are output when the list is called.

There should be a paginated output, at least when JSON or HTML is output. I'm not so sure it makes that much sense when exporting a calendar or an RSS feed....

Currently the default output is text/html but as it's an API it would be much easier to have application/json as the default and output HTML when text/html is provided via an Accept-Header

Logged in users shall be able to mark CfPs as interesting.

They shall be able to select whether they want to be notified about marked CfPs only.

Manually addd CfPs contain more valuable informations than the automattically parsed ones. therefore those informations shall not be overwritten by automated inserts/updates

For manually submitted events, the submitter should be able to include more or less any data that they deem relevant to speakers who may submit -for example:

• Speaker Package
• Requested Topics
• Talk Types (tutorial, workshop, etc.)

Perhaps this additional 'meta' data could be stored as a JSON object to make it flexible to whatever the user wants to add?

While running composer install I got a 404 for dependency aporat/slim-json-helpers. The repo either doesn't seem to exist anymore or is private now.

The only usage is in Callingallpapers\Api\Middleware\Renderer.

A user shall be able to create a third-party app to use token and secret to create events via the API.

The idea is to allow users to use f.e. a plugin to OpenCFP to submit the CfP directly to the API.