Brady had some good questions.. listing them w/ answers here:
1) It looks like there's much more info available apart from simply artists and their artwork. Are you guys looking for apps to include all the given information, or is it allowed to leave bits out (eg. not have events or bits of venue info such as types of restrooms)? Essentially, is this more of a general app related to artists in Austin or an app exclusive to the East Studio Tour?
answer: The app is not exclusive to the East Studio Tour, although it could be if you desire. The Hackathon app should focus on the experience of both the artist and the patron. The specific goal is to enable the artist to distribute their art through social media in a way that helps them get a bigger market for their work. The tour admin functions are not in scope.
2) The venue schema includes the artists for each venue but not the artworks themselves. However, it looks like actions have been added to the Art API. So I'd like to know if the api allows retrieval of an art piece by its venue_id (or medium, or artist, etc.) rather than just the id, something like /art?venue_id=123 to retrieve all art pieces in a particular venue.
answer: Currently, all art pieces in a venue are not included in Big Mediums data set. It's just artist and venue. This segues into you're next question a bit, but part of the goal of this app is to allow artists to upload their work so viewers have a better idea of what will be on display at each studio.
3) Seeing as there are no POST or PUT capabilities, we're curious as to what an artist can actually do with the app. Is all their data added some other way and the app simply displays it? Should the app allow artists to edit their pieces' information or use the device's camera to upload photos via the app? This is all specified in the requirements, but the lack of write functionality in the api threw us off, though we understand if that is to be added later. :-P
answer: We're planning to work on the interfaces for POST and PUT tonight! It's going a little slow because its our first flask project :)
7 comments
Will Lowe Manager • over 12 years ago
We're waiting on Big Medium to provide the data and we will expose the API this week. I'll update this thread when it's published.
Will Lowe Manager • over 12 years ago
Just got word from Big Medium. API will be published in the next day or two.
ThatWebGuy • over 12 years ago
Any update on the API release? Would love to know how much will be open to us before the 15th.
Will Lowe Manager • over 12 years ago
Yes, sorry for the delay. It will be up by the end of the weekend. I'll post a notification here as soon as it's published.
ThatWebGuy • over 12 years ago
Awesome. Thanks!
nynymike Manager • over 12 years ago
I am checked the API code into GitHub.
https://github.com/ArtAPI/artFlask
I am still working on this, but if you check this out, the documentation for the API is under
artFlask/_build/html/index.html
I'm going to deploy this soon, and will publish the links.
Will Lowe Manager • over 12 years ago
Brady had some good questions.. listing them w/ answers here:
1) It looks like there's much more info available apart from simply artists and their artwork. Are you guys looking for apps to include all the given information, or is it allowed to leave bits out (eg. not have events or bits of venue info such as types of restrooms)? Essentially, is this more of a general app related to artists in Austin or an app exclusive to the East Studio Tour?
answer: The app is not exclusive to the East Studio Tour, although it could be if you desire. The Hackathon app should focus on the experience of both the artist and the patron. The specific goal is to enable the artist to distribute their art through social media in a way that helps them get a bigger market for their work. The tour admin functions are not in scope.
2) The venue schema includes the artists for each venue but not the artworks themselves. However, it looks like actions have been added to the Art API. So I'd like to know if the api allows retrieval of an art piece by its venue_id (or medium, or artist, etc.) rather than just the id, something like /art?venue_id=123 to retrieve all art pieces in a particular venue.
answer: Currently, all art pieces in a venue are not included in Big Mediums data set. It's just artist and venue. This segues into you're next question a bit, but part of the goal of this app is to allow artists to upload their work so viewers have a better idea of what will be on display at each studio.
3) Seeing as there are no POST or PUT capabilities, we're curious as to what an artist can actually do with the app. Is all their data added some other way and the app simply displays it? Should the app allow artists to edit their pieces' information or use the device's camera to upload photos via the app? This is all specified in the requirements, but the lack of write functionality in the api threw us off, though we understand if that is to be added later. :-P
answer: We're planning to work on the interfaces for POST and PUT tonight! It's going a little slow because its our first flask project :)