nextcloud / nextcloud/contacts

Show summary after import (total, imported, skipped by dublicate-check, skipped by error), raw download of "skipped by error"-contacts

Open
#493 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: import
Dominant language
JavaScript
Stars
642
Forks
220
Avg merge
14h 39m
Merged PRs (30d)
51

Description

FEATURE REQUEST:

At the moment it is hard to investigate, which "Contact could not created" as an error message told me while import is in progess.

Exporting the contacts list and doing a diff with the import file is cumbersom, because sort order of contact items is different. Imagine an import file with hundrets of contacts (e.g. 302 contacts)

Please generate a "skipped by error"-contacts vcf file (raw data of that contact as in import file) and provide a download link to it after import, to enable easyer "debugging".

Please skip import for contacts that already exists in a nextcloud address book (with 100% the same contact data). Importing a vcf file (302 contacts) twice in the same address book of the same webuo user should not produce 2x 302 contacts in nextcloud. Skipped contacts should not be added to the "skipped by error"-contacts vcf file.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name files or tests. Start by locating the contact import flow and its post-import UI, then trace how duplicate and error cases are handled. Done means the import reports total, imported, duplicate-skipped, and error-skipped contacts, and offers the error-skipped contacts as a downloadable raw VCF without including duplicates.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.