A personal Leica Lens Register?

[01maciel]

Advertisement (gone after registration)

I have been working on a project every now and then to code an application for home users. The project can be described as a Leica Lens Register with some additional information for personal use. I know there are a lot of lists of lenses on the Internet. But none of them satisfies my need to enrich the lens data with my specific information, e.g. Date of Purchase, Dealer, Price tag etc.
The project is not a web based application since my experience in coding Web based GUI front ends is very limited, practically none existent. So it'll be a fat client. And there is another catch I'll tell later on.
The basis for the project is a simple (SQL) database with a few tables and fields. I am using the lens information freely accessible on the Internet, in particular the LUF/Lens Wiki. I imported the information with a semi automatic procedure. The import job has not been finished yet as all Leica lenses greater than 50mm are still missing. So far so good.
Here some screen captures from my computer of some very early results. Please keep in mind that this pre-alpha or much better: a proof of concept;)

First of all, the main form and a simple menu structure:

Welcome, dear visitor! As registered member you'd see an image here…

Simply register for free here – We are always happy to welcome new members!

 

The next screen capture shows an overview of all lenes in the Lens Register using a dynamic grid structure.

 

A click on the button on the right hand side at the top opens up yet different view of all lenses in a so-called treeview:

 

A double click on a specific lens opens up the corresponding lens details (next screen capture). I'm very sorry the form looks pretty ugly, fields are too tiny and all this is unsorted. But the form is still under heavy construction. In the end it is supposed to show all information about the specific lens you double clicked before. Some of the fields are empty as there is no information available.

So, what's the reason for this thread? In order to move on with the project I am asking for some information: What else (apart from the shown fields and attributes) decribes a lens? What kind of information is not shown in the last screen capture but is IYHO required? What could you think of? What else should be implemented?

And don't forget: this is a just-for-fun project. When the application is finished I am happy to share it with you.

 

[Advertisement]

The Leica Q3 is available for pre-order at B&H Photo Video and Adorama

[Guest]

4 minutes ago, 01maciel said:

What kind of information is not shown in the last screen capture but is IYHO required? What could you think of? What else should be implemented?

For M lenses: whether they are coded

For R lenses: whether they have ROM

[01maciel]

Thanks

vor 10 Minuten schrieb Joachim_I:

For R lenses: whether they have ROM

👍

vor 10 Minuten schrieb Joachim_I:

For M lenses: whether they are coded

This is the field "Lens Coding", example "011000"

[UliWer]

vor 29 Minuten schrieb 01maciel:

What else should be implemented?

It already looks very good - almost too much of details which will not be available in many cases (e.g. actual besides nominal focal length). Perhaps only one idea: catalogue numbers were only introduced around 1960 - before they used the five letter codes, often with additions for the mount. I dont know if your field "Order no." would accept letter codes.  

I don't know if the attributes are connected to other fields: e.g. usually chrome and black versions have different catalogue numbers, so this could be helpful. Same for the connection between serial no. and version - though this might have a high risk of faults. 

[Ecar]

A few field suggestions (unless I missed them):

The actual production date when available?

Condition at time of purchase? (eg, new or used)

Purchase price?

Some free text for additional info on accessories (eg, hoods, filters, ...)

Info on CLA (date, who/where, etc.)

[evikne]

This project looks so cool! I am looking forward to see it when it's finished, although I understand it can never be 100% complete. I have actually made a similar, but much less extensive register, and only for my own lenses. There I also have a field for "focus throw", for example 120°. This is something I find of interest when I am considering a new lens. But it's hard to find on the web, so I have used my own measures for this, and for net weight and length.

Edited February 5, 2021 by evikne

[lct]

Advertisement (gone after registration)

Great idea. I would put the code or catalogue numbers ("order no") at a higher level. Easier to search lenses when knowing those numbers. Also 21/4 above 21/3.4 but it is a detail.

[01maciel]

vor 3 Stunden schrieb Joachim_I:

For R lenses: whether they have ROM

Is this a y/n answer or do have ROM R-lenses any additional information like version, no, ...?

[evikne]

Type of focus ring (tabbed / ribbed / scalloped)?

All three are presented in your first picture. 

[colonel]

serial numbers ?

[01maciel]

vor 2 Stunden schrieb UliWer:

It already looks very good - almost too much of details which will not be available in many cases (e.g. actual besides nominal focal length). Perhaps only one idea: catalogue numbers were only introduced around 1960 - before they used the five letter codes, often with additions for the mount. I dont know if your field "Order no." would accept letter codes.  

I don't know if the attributes are connected to other fields: e.g. usually chrome and black versions have different catalogue numbers, so this could be helpful. Same for the connection between serial no. and version - though this might have a high risk of faults. 

Indeed there are too much of details. All these information are already available more or less as bulk data. It needs a lot of effort to go through it and to re-arrange to use it in a database. At some point it will be useful to categorise the details eg. a) personal information of purchase, focal thingies, etc.

Yes, "Order no. " is a TEXT attribute.

Wrt to the connected fields: it'll be a big job to implement some logic and caveats in the GUI or in database. I guess the job would be too big for me. I'll keep up with KIS, keep it simple.

[01maciel]

Excellent points - I added in the database so far:

• Type of focus ring
• Focus throw
• Condition at time of purchase
• Purchase price

A field for serial numbers is already there (see last picture at ~1100). Free text is available in the big field "Notes".

There is one unanswered question re the ROM for R-lenses.

CLA and production date incl. order no range is on my TODO list as it requires a 1:many relation. 1 lens : many CLA (perhaps) / 1 lens : many batches with different order nos

[lct]

17 minutes ago, 01maciel said:

Yes, "Order no. " is a TEXT attribute

It should not be modified if it means code number or catalogue number. Or do you mean "order no." otherwise?

Edited February 5, 2021 by lct

[01maciel]

vor 17 Minuten schrieb lct:

It should not be modified if it means code number or catalogue number. Or do you mean "order no." otherwise?

I see, code number / catalogue number is not equal to order no.  But: code number = catalogue number. Correct?

[evikne]

In my register also I have a field named "Purchased from" next to Purchase price, to enter the name of the store or a private seller.

BTW, I have also fields for "Sold to", "Sold price" and "Sold date" to keep track of lenses I no longer own. 

Edited February 5, 2021 by evikne

[lct]

7 minutes ago, 01maciel said:

I see, code number / catalogue number is not equal to order no.  But: code number = catalogue number. Correct?

Yes but it can be called "order no." too. 11663 for the 35/1.4 FLE by example. I just wanted to say that whatever way you call it the product number of the lens should no be editable and could be mentioned usefully at a higher level of info.

[pgk]

Your 'treeview' could be split up into 'variants' - chrome/black/knurling type/filter thread type/etc. For some lenses there may only be one variant, for oter there could be a significant number.

[01maciel]

One more question. Is it helpful to categorise the amount of details like I did with tabs in the screenshot?

• Focal Specifics
• Lens Details
• Techn. Data
• Misc

Welcome, dear visitor! As registered member you'd see an image here…

Simply register for free here – We are always happy to welcome new members!

[Advertisement]

Hallo,

Look here: Leica M

[evikne]

13 minutes ago, 01maciel said:

One more question. Is it helpful to categorise the amount of details like I did with tabs in the screenshot?

Looks great! Much simpler and clearer.

[Guest]

6 hours ago, 01maciel said:

Is this a y/n answer or do have ROM R-lenses any additional information like version, no, ...?

Just yes or no.