Skip to content

Commit 32eb32f

Browse files
committed
updated doc deps
1 parent 67c2d29 commit 32eb32f

8 files changed

Lines changed: 18 additions & 19 deletions

File tree

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
1-
mkdocs==1.3.0
2-
pygments==2.15.0
3-
pymdown-extensions==10.0
4-
pyyaml==6.0.1
5-
mkdocs-markdownextradata-plugin==0.2.5
1+
mkdocs==1.6.1
2+
pyyaml==6.0.3
3+
pymdown-extensions==10.16.1
4+
mkdocs-markdownextradata-plugin==0.2.6

docs/core-services.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ The Data Stations are trusted repositories (some are still in the process of bei
3131
are **not Data Stations**, as they are not in themselves full trusted repositories. In the technical architecture, however, they are described as variations on
3232
the [Data Station architecture](./datastation.md), as they are built using mostly the same [components].
3333

34-
[components]: ../components/
34+
[components]: components.md
3535

3636
### DataverseNL
3737

docs/dans-microservices.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ export is archived in the DANS Data Vault.
3030

3131
Service that manages a [Data Vault Storage Root] and provides a REST API for interacting with it.
3232

33-
[Data Vault Storage Root]: ../data-vault-storage-root/
33+
[Data Vault Storage Root]: data-vault-storage-root.md
3434

3535
| Docs | Code |
3636
|-------------------------------------|------------------------------------------------------------------|
@@ -63,11 +63,11 @@ Command line tool for interacting with the [Dataverse] service. It uses [dans-da
6363
|------------------------------------|-----------------------------------------------------------------|
6464
| [dd-dataverse-cli]{:target=_blank} | <https://github.com/DANS-KNAW/dd-dataverse-cli>{:target=_blank} |
6565

66-
[Dataverse]: ../dataverse/
66+
[Dataverse]: dataverse.md
6767

6868
[dd-dataverse-cli]: https://dans-knaw.github.io/dd-dataverse-cli/
6969

70-
[dans-dataverse-client-lib]: ../dans-libraries/#dans-dataverse-client-lib
70+
[dans-dataverse-client-lib]: dans-libraries.md#dans-dataverse-client-lib
7171

7272
!!! note "Replacement for dans-datastation-tools"
7373

@@ -216,7 +216,7 @@ Service that manages a catalog of all Dataset Version Exports in the [DANS Data
216216

217217
[dd-vault-catalog-cli]: https://dans-knaw.github.io/dd-vault-catalog-cli/
218218

219-
[DANS Data Vault]: ../data-vault-storage-root/
219+
[DANS Data Vault]: data-vault-storage-root.md
220220

221221
## dd-vault-ingest
222222

docs/data-archive.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ SURF Data Archive
33

44
[Data Archive]{:target=_blank} is a tape storage facility provided by [SURF]{:target=_blank}, the collaborative ICT organization for Dutch education and
55
research. It is used by the DANS Data Vault service to store its finished layers. The interface to Data Archive is provided by the `dmftar` utility, which is
6-
provided by SURF as open source software. See [Data Vault Storage Root](../data-vault-storage-root#serialization-in-layers) for more information about the DANS
6+
provided by SURF as open source software. See [Data Vault Storage Root](data-vault-storage-root.md#serialization-in-layers) for more information about the DANS
77
Data Vault layers.
88

99
[Data Archive]: {{ data_archive_url }}

docs/data-vault-storage-root.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ future users, rather than current ones.
1414
Do not confuse the DVSR with the [service interface of dd-data-vault], which is an internal microservice interface that is used by the [transfer service] to
1515
store data in the Data Vault.
1616

17-
[service interface of dd-data-vault]: ../dans-microservices/#dd-data-vault
17+
[service interface of dd-data-vault]: dans-microservices.md#dd-data-vault
1818

19-
[transfer service]: ../dans-microservices/#dd-transfer-to-vault
19+
[transfer service]: dans-microservices.md#dd-transfer-to-vault
2020

2121

2222
OCFL repositories
@@ -91,6 +91,6 @@ DMFTAR archives. This utility is the interface to the tape storage system.
9191
is just a lightweight wrapper around a TAR archive, implemented as a directory containing batches of (possibly multi-volume) TAR files along with index
9292
files and a checksum file.
9393

94-
[dans-layer-store-lib]: ../dans-libraries/#dans-layer-store-lib
94+
[dans-layer-store-lib]: dans-libraries.md#dans-layer-store-lib
9595
[Data Archive]: {{ data_archive }}
9696
[dmftar]: {{ dmftar }}

docs/datastation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Actors
1515

1616
* **Data Station User** - a user of the Data Station, typically a customer who downloads or deposits data.
1717
* **Data Manager** - a user with special privileges, who curates and publishes datasets submitted for review by a user.
18-
* **SWORD2 Client** - a software client that interacts with the [DANS SWORD2 Service](../dans-microservices/#dd-sword2).
18+
* **SWORD2 Client** - a software client that interacts with the [DANS SWORD2 Service](dans-microservices.md#dd-sword2).
1919

2020
Schema Legend
2121
-------------

docs/dataverse.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,15 @@ Dataverse provides event hooks that allow to configure workflows to run just bef
1313
workflows can have multiple steps. A step can be implemented as part of Dataverse or as an external service. The
1414
following microservices are configured to run as `PrePublishDataset` workflow steps:
1515

16-
* [dd-vault-metadata](../dans-microservices/#dd-vault-metadata)
16+
* [dd-vault-metadata](dans-microservices.md#dd-vault-metadata)
1717

1818
The following microservices are candidates to become part of the `PrePublishDataset` workflow in the future:
1919

20-
* [dd-virus-scan](../dans-microservices/#dd-virus-scan)
20+
* [dd-virus-scan](dans-microservices.md#dd-virus-scan)
2121

2222
The **BagPack export** flow step is implemented in Dataverse and is used to create an export of the published dataset version (a "Dataset Version Export" or
2323
DVE). The export complies with the [RDA's BagPack recommendation]{:target=_blank}. This exported bag is then picked up
24-
by [dd-transfer-to-vault](../dans-microservices/#dd-transfer-to-vault).
24+
by [dd-transfer-to-vault](dans-microservices.md#dd-transfer-to-vault).
2525

2626
| Docs | Code |
2727
|-----------------------------|-----------------------------------------------------|

docs/vaas.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,4 +16,4 @@ Components
1616
The "Vault as a Service" configuration has mostly the same components as a Data Station. The main difference is that Dataverse is not part of the configuration.
1717
Instead, a new component, [dd-vault-ingest]{:target=_blank}, is introduced to convert the datasets into RDA compliant bags and transfer them to the Data Vault.
1818

19-
[dd-vault-ingest]: ../dans-microservices/#dd-vault-ingest
19+
[dd-vault-ingest]: dans-microservices.md#dd-vault-ingest

0 commit comments

Comments
 (0)