how will photo integration be handled, and what photo servers are accepted
Most similar sites only integrate one photo server (such as panoramio). Photo integration should follow one of three possible scenarios: 1-uploader can choose from among at least a few options to host their photos (thus not being potentially required to sign up for yet another photo host)
2-content edit page provides an upload photo feature and logs into a selected server automatically to store photos (ie. ALL photos are stored on a THS account on one photo host)
3-all photos are stored on a THS server (such as within the SQL database, or to a folder on the THS server)
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Good progress
- Milestone target:
- None
- Started by
- Janos Gyerik
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
To respond to the proposals in the original description:
1- Uploaders can choose from photo hosts: yes, users can upload photos to *any* host, but they have to use the user interface provided by the host. Once photos are uploaded, add their URL's on the AkibaMap location editor interface to associate them with the location. e photo.
2- Content editor provides upload interface to photo host: no, users must use the interface of the photo host, and then add the photo URL to the location.
3- All photos are stored on a THS server: yes, this is already implemented. In addition, it might be nice to upload to a THS account on a photo host at the same time. Added a task for this.
https:/
