coremedia / content-hub-adapter-filesystem Goto Github PK

I set up my filesystem adapter to have connection ID ImportFiles and root folder /coremedia/localfiles.

When opened first time, the folder is shown as localfiles and files can be imported.

When clicking on "Reload Files" in library, resource is suddenly renamed (from localfiles to ImportFiles which is my connection ID). From there on, no contents are shown any longer until I restart Studio server.

This problem applies to code from branch master (as independent plugin).

Documentation on configuration of the adapter is wrong. It states in editorial-quick-start.md that a setting rootPath needs to be set. It should rather read rootFolder (like in the accompanying screenshot of the documentation).

While at it, error checking and messaging can be improved. If indeed rootPath is used as settings name, the resulting error message does not help in finding the culprit:

2021-02-05 08:35:40 - [ERROR] com.coremedia.contenthub.lib.ContentHubManager [] - Failed to initialize adapter for connection 'localfiles': null (http-nio-8080-exec-5)

Settings should be checked beforehand.

Furthermore, some settings (and documentation) need an overhaul:

• It looks like factoryId must be set to filesystem. This should be documented.
• This setting factoryId seems to be used as top-level node name in Studio library (unlike RSS adapter where the factoryId is rss but the top-level node is labelled RSS Feeds).
• Setting displayName does not seem to do anything. My folder /coremedia/localfiles is displayed as localfiles in Studio library.

This problem applies to code from branch master (as independent plugin).

Workspace needs to be built with CoreMedia-internal Maven repository (repository.coremedia.com). Otherwise, the build fails.

Unlike Blueprint workspace, the repo is not defined in POMs. It should at least be documented what repo to connect to.

This problem applies to code from branch master (as independent plugin).

The Type label for file system resources in Studio library is always filesystem_file.

This problem applies to code from branch master (as independent plugin).