Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • M micropublication
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • micropublication
  • micropublication
  • Issues
  • #204

Closed
Open
Created Sep 09, 2019 by Yannis Barlas@yannisMaintainer

User management

Let me make a proposal on how to move forward, so that we don't get stuck on this issue for long.

Users will have:

  • A single name/surname
  • A single username
  • A single password
  • Multiple connected emails (with one marked as "primary" - this is where notifications will be sent to)
  • Multiple affiliations

Emails and affiliations will be completely decoupled for flexibility.

When a user creates a submission, we'll capture a snapshot of their name at that point in time.
This way, if they change their name, it won't retroactively change the name for old articles, but will only affect new submissions.

Same logic of a snapshot will be applied to affiliations, so that old articles retain the affiliation they had at the time of submission.

Assignee
Assign to
Time tracking