NetX DAM

NetX DAM connects Drupal to a NetX digital asset management system.

Editors can browse NetX from the Drupal admin, add NetX assets as Drupal media, and refresh them later. The original files stay in NetX: a media item stores only the NetX asset ID, and the name, dates, dimensions and thumbnail are read from NetX.

The project is one core module plus submodules, so a site turns on only what it needs. Turning a submodule off removes its capability. Disabling the upload module removes every path that can write to NetX.

**Status: alpha.** It has been run on Drupal 11.3 and 11.4, but only against a mock NetX API, never a real NetX instance. Expect differences, and please report them.

Features

• A NetX API client with per-source configuration. The API token lives in the Key module.
• A media source for NetX assets (any asset type, optionally limited by file extension), with thumbnails, metadata mapping and an image formatter.
• A read-only explorer in the admin: folders, search and paging, with "Add" and "Update" actions per asset.
• An upload form that sends files from Drupal to NetX, with its own restricted permission.
• Webhooks: NetX events arrive verified and are dispatched as Drupal events. Your own code decides what to do.
• -Extension points as events: metadata, thumbnail URLs, explorer actions and badges, and webhooks. An example module shows each one with tests.

Modules

Module Machine name What it does NetX DAM netx_dam The core: API client, NetX source configuration, events NetX DAM Media netx_dam_media Media source, thumbnails, metadata, image formatter, add and update actions NetX DAM Explorer netx_dam_explorer Read-only admin browser NetX DAM Push netx_dam_push Upload from Drupal to NetX NetX DAM Webhooks netx_dam_webhooks Receive and verify NetX webhooks NetX DAM Example netx_dam_example Developer examples. Not for production

Post-Installation

How does this module actually work once I install it? Should I go to a config page? Should I look for a new content type? Should I go and manage my text formats? Provide an overview of the configuration process and any other special considerations for the module.

Not built yet: placing a NetX collection, folder or search on a front-end page.

Additional Requirements

• Drupal 11.3 or later
• Key Module
• A NetX account and an API token. Use a dedicated system user with only the permissions the site needs.

Getting started

Install with Composer, enable the modules you want, then follow the step-by-step guide in the project's docs/getting-started.md. It starts from what you want to do and tells you which modules and permissions you need.