Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
C
CommonsPub Federated Server
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1
    • Merge Requests 1
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Bonfire
  • CommonsPub Federated Server
  • Issues
  • #6

Closed
Open
Opened Mar 23, 2020 by Lynn Foster@lynnfosterMaintainer

Intents - validations

This is to define the validations required for the first iteration of Intents (offers and requests). As previously defined:

  • action is required
  • provider or receiver is required
  • (I don't think anything else is required, in combination or singly, in deference to the simplest implementations of intents, which are basically text)

Perhaps for CommonsPub the backend should conform to that; but UI or some other app-based piece can require more fields to allow more flexible for the various apps. Suggestions for the initial apps for intents:

  • name required (only if no Proposal with a name)
  • resourceClassifiedAs or resourceConformsTo required (although we may want to think more about this as we see how the taxonomies develop)
  • resourceQuantity or effortQuantity or availableQuantity required (resource or available quantity is for items, effort is for work or usage -- and I'm not sure if we do want to actually require a quantity, let's explore the requirements a bit more too; but quantity will be needed to more accurately match or simulate potential flows)
  • finished (would be good to initialize to false in the backend if not provided, which it wouldn't be on create)
  • inScopeOf required for any app which has intents always in the context of a group (only if Proposal.inScopeOf not there)
Edited Mar 23, 2020 by Lynn Foster
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: bonfire-ecosystem/Server#6