Hi,
But he could change it using an photo editing application. So then he
might want to track the date of changes.
Regards,
Prabhath
On Fri, Jun 1, 2012 at 12:55 AM, Avdhesh Yadav a...@avdheshyadav.com wrote:
On Thu, May 31, 2012 at 10:37 PM, Prabhath Suminda
pathiranap...@gmail.comwrote:
Hi,
I developed following schema to store metadata. Please give feed backs and
improvement on this.
This table is the main table which contains data about photoes.
PhotoURI (Primary key)
PhotoNickName
Location
Date
Time
LastModifiedDate
I think LastModifiedDate is not required..I think user is not going to
modify Image using our application ?
By using photoURI we can uniquely identify each photo stored in the
device.
I am planing to add a autocomplete list to select the location of the photo
using Google maps API.
Last modified date cannot be changed by the user.
If the user is capturing the image through our application Location date
and time will be automatically generated.
Below table is used to represent the one to many relationship between a
photo and people in it. Name column may refer to people in phone contacts
or custom names.
PhotoURI
Name
By Implementing and populating this schema we will be able to query
photoes using different attribute combinations.
On Mon, May 28, 2012 at 11:18 PM, Prabhath Suminda
pathiranap...@gmail.comwrote:
Hi,
A created this Google doc to show the current progress of the project.
Please review it and give feedback.
https://docs.google.com/document/d/1fEGQZiuwr0GNUyYcngJru2-g4oUMN5zK0_zVdfwLwGY/edit
The metadata I have planned to impalement is photo nick name (e.g
my favorite photo),, date, time, people in it, location. Are there any
missing ones? After I finalized this requirement I will design a database
schema for storing these stuff and submit it for review.
Regards,
Prabhath
--
Avdhesh Yadav
http://www.avdheshyadav.com
http://twitter.com/yadavavdhesh
