Member Junction
    Preparing search index...

    Autotag provider for MJ entity records. Uses the EntityDocument template pipeline to render records into text, creates EntityRecordDocument snapshots, links them to ContentItems, and feeds the text through the LLM autotagging pipeline.

    Configuration is driven by ContentSource.EntityID and ContentSource.EntityDocumentID rather than the legacy ContentSourceParam key/value approach.

    Hierarchy (View Summary)

    Index

    Constructors

    Properties

    _provider?: IMetadataProvider

    Optional provider override; falls back to Metadata.Provider when not set.

    contentSourceTypeID: string
    IsPushOnly?: boolean

    True when items are pushed into this source on demand (such as AutotagUpload) rather than pulled by walking an external listing. Discover and Sync skip push-only sources with a Skipped outcome and never mark their items as orphans.

    SupportsExhaustiveWalk: true

    True when a driver's walk with Since = null is guaranteed to visit every live top-level item in the source, so Discover in Mode: 'Sync' can safely mark unvisited items for deletion. Drivers backed by bounded/windowed feeds (like RSS) leave this unset or false.

    Accessors

    Methods

    • Run autotagging for this source type.

      Parameters

      • contextUser: UserInfo

        The user context for server-side operations

      • OptionalonProgress: AutotagProgressCallback

        Optional progress callback

      • OptionalcontentSourceIDs: string[]

        Optional filter: only process these specific source IDs. If omitted, processes all sources for this type.

      • Optionalprovider: IMetadataProvider

        Optional metadata provider override; defaults to Metadata.Provider

      Returns Promise<number>

      the number of content items processed (new + retried)

      Legacy autotagger entry point. Implement Discover and optionally Fetch for the Content Pipeline Framework (@memberjunction/content-pipeline).