-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
People need more metadata #76
Comments
What do you think about #79? |
@degan6 @issmirnov It looks like it is a grate idea. This way the user have the freedom of adding the proper details for any person. nice work guys. 👍 . I personally support the Idea. Another thing I would like to separate All the forms error message for each input instead of echoing out all the messages like this |
A great resource for data too is Gravatar which if you have someone's email address can pull in any information they have published there beyond their photo, for example websites and social accounts Here's an example for my account: https://en.gravatar.com/mkaz.json Would need the fields and then it would be pretty straight-forward to pull in the data when initially creating the Contact once the email is entered to help fill out the form. |
I think this, like #79 , should be handled very carefully. Before moving forward with a PR for this, let's discuss how we can achieve this, because the product has to remain extremely simple. |
I agree, I think #79 has a better discussion and more fleshed out ideas for how to get it done. I'm going to close this out as a dub. |
Dub of #79 |
This issue has been automatically locked since there |
Most people have more than one email and phone number, plus websites, twitter username.
I think adding something were we have a either a table for each type of data like the email table, address table, phone number table and so on. That might not scale well so an alternative is to make a general person metadata table and have a name and value column relating to one person.
The second approach isn't great database design but allows for any data to be stored about a person.
I am looking forward to getting this going with a pull request or two but any wondering what everyone thinks is the better way to go
The text was updated successfully, but these errors were encountered: