# InvenioRDM Alpha 5 (March Release)

**URL:** <https://invenio-talk.web.cern.ch/t/inveniordm-alpha-5-march-release/90>\
**Category:** Invenio RDM\
**Created:** [31 March 2020 11:54 UTC](https://invenio-talk.web.cern.ch/t/inveniordm-alpha-5-march-release/90 "2020-03-31T11:54:38Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ppanero](https://invenio-talk.web.cern.ch/user_avatar/invenio-talk.web.cern.ch/ppanero/32/40_2.png) [@ppanero](https://invenio-talk.web.cern.ch/u/ppanero)\
**Post date:** [31 March 2020 11:54 UTC](https://invenio-talk.web.cern.ch/t/inveniordm-alpha-5-march-release/90/1 "2020-03-31T11:54:39Z")

</div>

March is ending, which means… April’s fools! No… just kidding 😉 **Release!**

Thank you all for testing and giving feedback on the February  
release, and your many contributions.

## Release Content

This release comes with new:

- Metadata extensions (also known as custom fields).
- Support for custom vocabularies.
- Deployment via Helm charts (and available Docker images  
[here](https://github.com/inveniosoftware/demo-inveniordm/packages/164273)).

Improved documentation, bug fixes and others!

### New deployments

We have also deployed two InvenioRDM instances:

- Demo site ([https://inveniordm.web.cern.ch](https://inveniordm.web.cern.ch)), which will host  
the latest monthly release (e.g. version 0.7.0). The corresponding  
documentation will be at [http://inveniordm.docs.cern.ch](http://inveniordm.docs.cern.ch).
- QA Demo site ([https://inveniordm-qa.web.cern.ch](https://inveniordm-qa.web.cern.ch)), which will  
host the `latest` changes during the development. The corresponding  
documentation will be at [http://inveniordm-qa.docs.cern.ch](http://inveniordm-qa.docs.cern.ch).

## What do you need to do?

Try out this release by using the documentation ([http://inveniordm.docs.cern.ch](http://inveniordm.docs.cern.ch)).  
Try to make it your own, we are mostly interested in you trying the new metadata  
extensions and custom vocabularies. If you have the chance, please try to deploy  
using the Helm chart.

As always here is the template to give feedback:

```auto
## Bugs

## What worked well

## What didn't work well

## Wishes for documentation

```

Thank you very much in advance, take care and stay safe!

**Annex**

We are still working on the datamodel and its presentation. Some fields are still required  
for the records UI to work correctly. A minimal record that would work is:

```json
{
    "_access": {
        "metadata_restricted": false,
        "files_restricted": false
    },
    "_owners": [1],
    "_created_by": 1,
    "access_right": "open",
    "community": {
        "primary": "Maincom",
        "secondary": ["Subcom One"]
    },
    "creators": [],
    "identifiers": {
        "DOI": "10.9999/rdm.9999999"
    },
    "resource_type": {
        "type": "image",
        "subtype": "image-photo"
    },
    "titles": [{
        "title": "A minimal record",
        "type": "Other",
        "lang": "eng"
    }],
    "descriptions": [
        {
            "description": "A story of a turn-key RDM!",
            "type": "Abstract",
            "lang": "eng"
        }
    ]
}

```

---

<div class="post-metadata">

**Author:** ![mb-wali](https://invenio-talk.web.cern.ch/user_avatar/invenio-talk.web.cern.ch/mb-wali/32/49_2.png) [@mb-wali](https://invenio-talk.web.cern.ch/u/mb-wali)\
**Post date:** [2 April 2020 10:28 UTC](https://invenio-talk.web.cern.ch/t/inveniordm-alpha-5-march-release/90/2 "2020-04-02T10:28:23Z")

</div>

First of all many thanks for your hard work. 🙂

My focus on testing this release was more on how to build my own image and use the image outside of `invenio-cli` environment and have to connect with external Database, Cache, and Elasticsearch machines. External meaning not in the same machine.

## Bugs

Build your own image.

## What worked well

The CLI works great.  
Demo Data.

## What didn’t work well

building your own image, using this command.

```auto
docker build -t demo-inveniordm /path/to/your/instance --build-arg include_assets=true

```

the image has been build with static errors, and while running image gives this error:

```auto
FileNotFoundError: [Errno 2] No such file or directory: '/opt/invenio/......./var/instance/static/dist/manifest.json'

```

### I solved this by replacing these lines of code in Dockerfile:

### from:

 ![from](https://invenio-talk.web.cern.ch/uploads/default/original/1X/58111abd0a19fbdc34c99a3c47f4d08373f3d41e.png)

### to:

![to](https://invenio-talk.web.cern.ch/uploads/default/original/1X/210d6a3c7f000fb66685deb0ddad7e9735ee52c9.png)

I am not sure if this was the issue.

## Wishes for documentation

1. I wish there was more information on building your own image.
2. How to run the database, cache, Elasticsearch scripts without `invenio-cli`, once you have your own image to use with an external Database/cache.

---

<div class="post-metadata">

**Author:** ![ppanero](https://invenio-talk.web.cern.ch/user_avatar/invenio-talk.web.cern.ch/ppanero/32/40_2.png) [@ppanero](https://invenio-talk.web.cern.ch/u/ppanero)\
**Post date:** [2 April 2020 16:46 UTC](https://invenio-talk.web.cern.ch/t/inveniordm-alpha-5-march-release/90/3 "2020-04-02T16:46:37Z")

</div>

Hi Mojib, Thanks for testing!!

Quick question, did you run it in the directory or you specified a path? meaning `/path/to/your/instance` was `.`or some other path?

Cheers,  
Pablo

---

<div class="post-metadata">

**Author:** ![mb-wali](https://invenio-talk.web.cern.ch/user_avatar/invenio-talk.web.cern.ch/mb-wali/32/49_2.png) [@mb-wali](https://invenio-talk.web.cern.ch/u/mb-wali)\
**Post date:** [2 April 2020 17:03 UTC](https://invenio-talk.web.cern.ch/t/inveniordm-alpha-5-march-release/90/4 "2020-04-02T17:03:24Z")

</div>

Hi Pablo, welcome!  
no 😂, path to directory where Dockerfile of my instance is.

Cheers,  
Mojib

---

<div class="post-metadata">

**Author:** ![ppanero](https://invenio-talk.web.cern.ch/user_avatar/invenio-talk.web.cern.ch/ppanero/32/40_2.png) [@ppanero](https://invenio-talk.web.cern.ch/u/ppanero)\
**Post date:** [3 April 2020 12:36 UTC](https://invenio-talk.web.cern.ch/t/inveniordm-alpha-5-march-release/90/5 "2020-04-03T12:36:19Z")

</div>

Hi Mojib,

You are right. I just realized that it would only work if you are in the directory of the instance. Therefore, the path is `.`. Otherwise, the `COPY . ` commands inside the Dockerfile would make it miss files.

Will address this for the next release.

For now, doing

`docker build -t demo-inveniordm . --build-arg include_assets=true`

Should work.

As for the changes, `invenio webpack buildall` calls the other three under the hood so there is no difference between those two Dockerfiles. Could you see if you can reproduce it with `.`?

Cheers and thanks a lot!  
Pablo

---

<div class="post-metadata">

**Author:** ![mb-wali](https://invenio-talk.web.cern.ch/user_avatar/invenio-talk.web.cern.ch/mb-wali/32/49_2.png) [@mb-wali](https://invenio-talk.web.cern.ch/u/mb-wali)\
**Post date:** [6 April 2020 08:50 UTC](https://invenio-talk.web.cern.ch/t/inveniordm-alpha-5-march-release/90/6 "2020-04-06T08:50:14Z")

</div>

Hi Pablo,

i have tried using the `.` while building the image, it works just fine.

but regarding the lines in the Dockerfile using this lines which is as default in Dockerfile.

```auto
RUN if ["$include_assets" = "true"]; \
   then \
       cp -r ./static/. ${INVENIO_INSTANCE_PATH}/static/ && \
       cp -r ./assets/. ${INVENIO_INSTANCE_PATH}/assets/ && \
       invenio collect --verbose && \
       invenio webpack buildall \
   ; fi

```

gives error while building images, bellow is some line of the error:

```auto
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
Error: Cannot find module 'node-sass'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (/opt/invenio/var/instance/assets/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
    at getDefaultSassImpl (/opt/invenio/var/instance/assets/node_modules/sass-loader/dist/index.js:198:10)
    at Object.loader (/opt/invenio/var/instance/assets/node_modules/sass-loader/dist/index.js:80:29)
    at runLoaders (/opt/invenio/var/instance/assets/node_modules/webpack/lib/NormalModule.js:316:20)
    at /opt/invenio/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:367:11
    at /opt/invenio/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:233:18
    at runSyncOrAsync (/opt/invenio/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:143:3)
    at iterateNormalLoaders (/opt/invenio/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:232:2)
    at Array.<anonymous> (/opt/invenio/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
    at Storage.finished (/opt/invenio/var/instance/assets/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
    at provider (/opt/invenio/var/instance/assets/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9)
    at /opt/invenio/var/instance/assets/node_modules/graceful-fs/graceful-fs.js:115:16
    at FSReqWrap.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:53:3)

ERROR in ./scss/invenio_theme/admin.scss
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
Error: Cannot find module 'node-sass'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (/opt/invenio/var/instance/assets/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
    at getDefaultSassImpl (/opt/invenio/var/instance/assets/node_modules/sass-loader/dist/index.js:198:10)
    at Object.loader (/opt/invenio/var/instance/assets/node_modules/sass-loader/dist/index.js:80:29)
    at runLoaders (/opt/invenio/var/instance/assets/node_modules/webpack/lib/NormalModule.js:316:20)
    at /opt/invenio/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:367:11
    at /opt/invenio/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:233:18
    at runSyncOrAsync (/opt/invenio/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:143:3)
    at iterateNormalLoaders (/opt/invenio/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:232:2)
    at Array.<anonymous> (/opt/invenio/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
    at Storage.finished (/opt/invenio/var/instance/assets/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
    at provider (/opt/invenio/var/instance/assets/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9)

```

and after image is build, using the image gives error of `manifest not found`.

there is some problem while building the assets/statics,  
anyway adding these lines fixed it for me.

```auto
       invenio webpack create && \
       invenio webpack install --unsafe && \
       invenio webpack build \

```

Thanks Pablo! stay safe 🙂

---

<div class="post-metadata">

**Author:** ![ppanero](https://invenio-talk.web.cern.ch/user_avatar/invenio-talk.web.cern.ch/ppanero/32/40_2.png) [@ppanero](https://invenio-talk.web.cern.ch/u/ppanero)\
**Post date:** [8 April 2020 16:12 UTC](https://invenio-talk.web.cern.ch/t/inveniordm-alpha-5-march-release/90/7 "2020-04-08T16:12:02Z")

</div>

Hi Mojib,

Thanks for the feedback. We will check it out. That is happening because for some reason the assets and templates are not in `.` and therefore not copied.

> [@mb-wali](#):
>
> cp -r ./static/. ${INVENIO\_INSTANCE\_PATH}/static/ && \ cp -r ./assets/. ${INVENIO\_INSTANCE\_PATH}/assets/ && \

Somehow the second call it is finding them. Might have to do with layers of the docker building.

As for `buildall` is equivalent to the other three. See [here](https://github.com/inveniosoftware/flask-webpackext/blob/607f1bb31cc3c51671ff91b0cad70f358f76a857/flask_webpackext/cli.py#L70). There is no programmatic difference. Calling buildall does create, install and build in one command.
