Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
E
eScriptorium
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 88
    • Issues 88
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • scripta
  • eScriptorium
  • Issues
  • #25

Closed
Open
Opened Jan 24, 2019 by Robin Tissot@rtissotMaintainer

Project management

We need to be able to store Documents in a folder/project/corpus for easier management. It is not clear yet what data should be stored there yet (to be shared between a corpus of documents), so some analysis is necessary.

I'd like to not have to differentiate technically between Project, Corpus and Collections, and have a two level structure (folder+document). Because i think most use cases can be solved with a search input (if metadatas are not enough to filter we can eventually add tagging). Also tree structures are often catastrophic performance wise and UI wise (select documents across the tree).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: scripta/escriptorium#25