nextcloud / nextcloud/contacts
Social Network parsing for imports
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 642
- Forks
- 220
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 51
Description
When I imported from Gmail, I had a lot of URL's in peoples records that were links to their social networking profiles. Because you can detect the string of twitter.com/___, you could probably re-write many of my imported links from full URL's to social media usernames. Maybe you could even have the parsed data for username pushed into a link testing function to see if your parsing guessed right. Same goes for the Instant Messaging contact object. I had URL's for people's Skype address.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Gmail import parsing entry point; the issue names no files, tests, or specific implementation path. Review how imported social-network and Skype URLs are represented before defining the supported parsing cases and validation behavior. Done should include agreed handling for the mentioned URL patterns and coverage for the resulting imported contact data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100