This is the bug tracker for Photo Organizer.
FS#185 - Development / printing information
Attached to Project:
Photo Organizer
Opened by Jiri Vasina (poutnik) - Thursday, 22 March 2007, 17:24 GMT-5
Last edited by Solomon Peachy (pizza) - Sunday, 06 January 2008, 11:03 GMT-5
Opened by Jiri Vasina (poutnik) - Thursday, 22 March 2007, 17:24 GMT-5
Last edited by Solomon Peachy (pizza) - Sunday, 06 January 2008, 11:03 GMT-5
|
DetailsI capture the majority of photos on film, process it myself, print or scan it myself. A lot of people my do the same. I would like to see an option to note down the way I developed the film. IMO it would be best done in the following fashion:
have a table with development instructions (could have fields like: "id"?, "name", "developer", "dillution", "time", "agitation", "temperature", "notes"). The editing would be done in a similar way as for locations. This info would than be linked (through the id field?) as a technical informaion for the photo. If there was the possibility to enter these information, I would not have to have a separate database/excel sheets noting this down. Thanks a lot Jiri |
This task depends upon
create table "developers" (
identifier integer unique not null,
manufacturer integer references manufacturers(identifier),
model text not null
);
create table 'development' (
identifier integer unique not null,
name text not null,
developer integer references delvelopers(identifier),
dilution text, -- a percentage?
time timestamp, -- ie "5 minutes 3 seconds"
agitation text, -- ?? "yes/no/light/heavy" ?
temperature integer, -- eg 24C
notes text
);
I don't know what kind of data types you'd have for each of these fields.
dilution text should be text field (it usually is something in the form "1:100", "1+1", "1+3", "1:1:100", ...)
time - could be the timestamp like that
agitation - definitely text, and sometimes a long one ("continuous agitation first 30sec, than one agitation every 2nd minute", "stand development",...)
.
There are only a handful ways used for development normally by one user - the ones he likes and gets good results with, so there would be on the order of tens of entries in the table.