ecdb is open now.

[lgrfbs]

Electronics Component DataBase have open the doors for the web.
http://ecdb.net/index.php

I hav been a beta-test on the system for some time and think this is a good idea.
Hope you will like it to, and no I are not the web page owner.

[Rufus]

Electronics Component DataBase have open the doors for the web.
http://ecdb.net/index.php

I hav been a beta-test on the system for some time and think this is a good idea.
Hope you will like it to, and no I are not the web page owner.

Who is going to risk the effort of entering a lot of data into a 'cloud' database which could simply disappear without trace at any moment?

[Psi]

I tried to register but apparently people with 3 letter first names aren't allowed to use the service.
It wont accept my nick either for the same reason.

[lgrfbs]

Both this issues are on the to do list and found after the developers open the doors to the service.
Hope this helps a bit.

[Stephen Hill]

I think I'll take a look at this. I currently use Google Spreadsheet to catalog all my components.

[ElectricMan]

Haha, I was just looking at Google Analytics and saw that there was visitors coming from eevblog!
Really fun to see!

I am the owner and creator of ecDB.
I have now changed so you, Psi and other can register with names/nicknames which is only 3 characters long.


Rufus:
I don't have any plans to make ecBD disappear.
But I can understand your worries. There have been a few people which is concerned about the same thing.
The plan is to make an export function, so you can export your own database to for example an excel-spreadsheet.


If you have any other suggestions, please tell me. That's how we are going to develop the site!

[Stephen Hill]

Hi ElectricMan,

Looks like a good tool and it's nice and simple which I really like.

The only thing I noticed right away was I was unable to enter specifics details about a component or add custom fields. As an example, when I'm entering a resistor I might want to record in separate fields: Resistance, Power Rating, Tolerance, etc...

Then when I'm browsing my components I can search and sort by these values.

Is this a feature you would consider implementing in the future?

Many Thanks
Stephen

[ElectricMan]

Yes, I have thought of that too, and I hope I can implement a feature like that in the future.
But for now you have to specify your special values and so on in the "comments" box for the component.


Here is a cutout of my list of the major features I want to implement:

Code: [Select]

Public components - complete that feature.
View to physical print the whole personal database. Monospace-text (old-school typewritten text), nice colums and so on!
Datasheet and picture uploading.
Advanced search with parameters.
Log book for each component. See when the component last was used/edited/bought etc.
Barcode implementation.
Import/export of text/spreadsheet file.
Fast edit of quantity from index.php etc.
Personal categories, fields.
Split the components on pages.


[Psi]

I am the owner and creator of ecDB.
I have now changed so you, Psi and other can register with names/nicknames which is only 3 characters long.

If you have any other suggestions, please tell me. That's how we are going to develop the site!

Thanks.

Maybe have the option "Automatically email me a csv/excel backup of my database every x months (if new data has been added)"
That way people get a backup automatically.
Users will feel better about trusting the service when they know they can only ever lose data added since the last backup email.

[Ajahn Lambda]

Is there a privacy policy in place?  I just want some assurance that my name and email won't be shared, spammed, or sold.

[mariush]

It would need to offer complete export functionality to trust it enough and use it.

Also it could use something like...

For some items like resistors, capacitors, diodes... it could be useful to have stored the diameter, space between leads, the form (0603 for example for smds), hFe for transistors...

allow user to enter some kind of product code from some big stores (digikey, farnell/newark, rs-online) and retrieve the product info from their pages... see if they have some api they'd be willing to give you access to like findchips dot com does.

have something to the form of :

bought from :

store name  ... store's unique id for the item ... how many items bought  ....  price of purchase for the set ....   1/10/50/100 piece price at purchase ... 

[ add batch ]  - i may order the part from several stores, depending on promotions or price variations and minimum quantities - sometimes it's worth waiting 10 days to get stuff from US, other times it's better to get from Europe even if a few dollars more expensive.

this way when i want to order more parts, the system could do a comparative search at all the online stores it recognizes and suggest the cheapest store based on the number of parts user wants and the conditions of the user (give more weight to stores user favors).

As in.. maybe I need 35 capacitors which are:

1.1$ each on Farnell or 0.75$ if bought a minimum of 50....
1$ on Digikey or 0.8$ for 10+ ...

So now I have several options:

1. get 35 from Farnell :  1.1$ x 35 + 4$ shipping (3 day delivery) = 42.5
2. get 50 from Farnell : 0.75$ x 50 + 4$ shipping = 41.5
3. get 35 from Digikey : 0.8 x 35 + 20$ shipping (free for orders above $200) = 48$ (+ about 3% customs fees if order above 150$)

Obviously i'll get 50 capacitors from Farnell even if I need only 35. But that could change if Digikey had 0.5$ for 100+ and I'm ready to do a $200+ order to get free shipping on Digikey , which I had it happen to me before.

[lgrfbs]

I think the ecdb is a database over were you electric parts is locate, not to be a site for the low price search system.

[jpelczar]

Retarded American System (Imperial) - ROTFL

I think the possibility to build footprint database (for Altium Designer, Protel, KiCad, Eagle, etc.) would be a killer feature.

[hlavac]

What I would really like is an universal footprint/symbol converter so I don't have to redo them, and a parametric search with source availability filtering