owncloud / owncloud/libre-graph-api

user.lastChangedDate for efficient retrieval of user updates

Open
#26 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Mustache
Stars
4
Forks
3
Avg merge
23h 14m
Merged PRs (30d)
1

Description

I noticed that, in responses, for user and identity.user objects only the user.identifier is provided, but not the displayName. I understand/guess this is probably for efficiency / performance reasons.

From the client perspective, however, this raises the question on how often to query the /users endpoint to retrieve information on users and keep it up-to-date.

My idea here is that I could probably use OData to query only for users whose records were created or updated since the last time the client checked. I'd need a lastChangedDate property for that, though.

All I could find was lastPasswordChangeDateTime, which tracks only password changes.

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

No file, test, or entry point is named. Start by locating the schemas and handlers for user and identity.user, then inspect how OData filtering is exposed for user records. Done means a lastChangedDate property is available and can support retrieving users created or updated since a supplied time.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend-api-design
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.