PubPub Platform Glossary

Learn the terms and concepts of PubPub Platform.

This is a auto-generated Article of all your definitions within the glossary.

Glossary

This is a auto-generated Article of all your definitions within the glossary.

  • Actions

    Actions are modular applet activities that can be taken on a Pub. Actions are configured on specific Stages, and can be triggered manually (by an Administrator or Editor on an individual Pub) or automatically (by a Rule on any Pub in that Stage).

  • Communities

    A Community is the top-level unit of PubPub Platform. Communities can represent a single book, a collection of books, a journal, a blog, a preprint server, a repository, or any other kind of Pubs. Users can invite Members to help manage a community with varying levels of permissions.

  • Dashboards

    Dashboards are where users manage Workflows, Forms, Types, Members, and Fields. Each of these configurations have a Dashboard where users can see useful information, search and organize content, and make changes to settings. To visit a specific Dashboard, click on the Dashboard name on the sidebar below “Manage”.

  • Elements

    Elements are the building blocks of Forms. There are two kinds of Elements: Fields and Structures.

  • Fields

    Fields are the bottom-level unit of PubPub Platform. Communities use Fields to define community-specific metadata. collected and arranged to create Types, Forms, and Pubs. Field Cards are used to display and arrange fields in the Forms Dashboard.

  • Forms

    A Form is a way to collect information to create, edit, and update Pubs. Admins can create and edit forms to collect information from Members. Forms are made up of Elements, like Fields and Structures.

  • Members

    A Member is someone who has permission to manage a part of your Community. Members can be given different permission levels, from Pub- and Form-specific to full admin access. They can be added to Communities or Pubs, allowing you to give specific people permissions to work on the entire Community, or just specific parts of it.

  • Pubs

    A Pub is the main content unit of PubPub Platform. A Pub can be journal articles, book chapters, reviews, conference papers, blog posts, supplementary material, or just about anything else you want. At their core, Pubs are collected content and metadata. Pubs can have relationships to other Pubs, including parent Pub, child Pub, and sibling Pub.

  • Rules

    Rules establish triggers for Actions, letting users schedule or automatically run an Action on or after a specific event or duration.

  • Stages

    A Stage is a step in a Community’s publishing process, where Pubs can be acted upon. Connected Stages make up a Workflow, the stages through which Pubs are intended to move from submission to publication.

  • Structures

    Structures are non-Field elements used to add context to forms. These include headings, dividers, and text blocks.

  • Tokens

    Tokens are objects used in emails and Forms to represent values within PubPub Platform, and can be used in Forms and Actions to populate certain fields.

  • Types

    Communities specify the kinds of Pubs they work with by defining a Type. A Type structures the content and metadata. For example, an overlay journal might have Types like Submission, Review, and Evaluation Summary.

  • Views

    Views are where users view activity of a Community, including the Action Log. To visit a View, click on the View name on the sidebar below “Views”.

  • Workflows

    Every Community has its own Workflows, defined sequences of connected Stages that a raw submission goes through on the path to publication. Every preprint server, for example, has its own moderation process; a journal, likewise, might conduct peer review on research articles, but not invited commentaries. Admins can create and edit Workflows for specific Types.