lucas42/lucos_contacts

A contacts list.

lucos_contacts's Issues

Prevent the same relationship existing twice

Merging people together can cause the same relationship to occur twice. This is just confusing (especially with inferred relationships getting added a result).

Refactor names

Rather than having name fields per language, allow agents to have multiple names. (possibly with a language attribute?)

Gift ideas formatting

Allow gift ideas to have newlines etc...

First request after a while returns a varnish 503 error

If django hasn't been used in a while, the next request made returns an error.

Potential fixes:

• Look for a setting to stop django shutting down
• Use varnish healthchecks as a keep alive
• Get varnish to retry after a failure
• Use zabbix monitoring as a keep alive (or maybe to check how frequently this happens).

Migrate contacts from old phone

Any point in caring about things on the HTC Hero?

Mark addresses as inactive

I'd like to be able to say "this address is an old one", without completely deleting it.

Probs the same for phone numbers and the like too.

Don't hardcode any domains.

Domains should vary by environment. Need to work out how to the list of hosts from lucos_services into django.

Places using hardcoded domains:

• Authentication
• Links to JS bootloader in templates
• Broken links to touch icon in templates
• JS adding link to admin page in menu

Merging people from different pages

Currently, the merge action is only available on the admin agent list view. This means if, due to pagination, two people end up on different pages, there's no way to merge them.

Look at other ways of triggering the merge action.

Improve account UX based on type

Currently all account types show the same fields. Ideally, these would auto-update based on the type selected. (even if it's just hiding the irrelevant fields).

Dependabot couldn't authenticate with https://pypi.python.org/simple/

Dependabot couldn't authenticate with https://pypi.python.org/simple/.

You can provide authentication details in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'.

View the update logs.

Search on homepage

Add clientside search bar which filters contact list to those matching the search term. Include non-primary names in search.

Sync contacts from facebook to lucos.

Import all friends for the authenticated user. Determine whether the following data can be gotten from facebook API:

• Name.
• Lists they appear in.
• Phone number.
• Other social media accounts.
• Relationship with authenticated user. (Or even with each other - should be able to infer relationships from that).

Also, it'd be useful to sync group (aka list) membership back to facebook.

Apply relationship inference logic to deletions.

At the moment, deleting a relationship only deletes that specific instance. (eg deleting a sibling relationship from Alice to Bob will still leave the relationship from Bob to Alice in place).

Ideally, the inference logic would go through all the relationships which imply the deleted relationship should exist and delete those to prevent inconsistencies.

Complexity
Whilst this is probably easy enough for inverses (and transitive?), it's hard to know what to do for multi-relation inferences.
Suppose a "nibling" relationship is deleted. This suggests that either a corresponding "sibling" relationship or "child" relationship is incorrect. However, there's no way to know for certain which of these to delete, as the other one may be perfectly valid.

Migrate contacts from lucos 1.0

These contacts are mainly social media, so not sure if there's much point.
Most useful bits would be linking multiple social media accounts to a single person, and also which groups people were added to.

This would only need to be a hacky one-off script.

Dev Database

Work out where to set up the database. Puppet? Init command in services.json?

Redirect to profile page after a saving an agent

Currently clicking save on an agent brings you to admin view listing all the agents.
Instead, it should bring you to the agent's profile page.

Make work offline

Pagination

Too many contacts on a single page is going to get annoying.

Load resources using common JS

Currently the live bootloader is being used, but in order to switch to the new dev one, CJS support will be required.

Order relations by closeness

At the moment, the order of people in the "Relations" section is the same order across everyone. It should be tailored for each person, so the closest relationships come first (eg parents & children before cousins etc)

Show non-primary names on agent view page