@@ -146,40 +146,6 @@ This creates a dummy dandiset with valid metadata and a single dummy asset.
146
146
The dandiset should be valid and publishable out of the box.
147
147
This script is a simple way to get test data into your DB without having to use dandi-cli.
148
148
149
- ### import_dandisets
150
- ```
151
- python manage.py import_dandisets [API_URL] --all
152
- ```
153
-
154
- This imports all dandisets (versions + metadata only, no assets) from the dandi-api deployment
155
- living at ` API_URL ` . For example, to import all dandisets from the production server into your
156
- local dev environment, run ` python manage.py import_dandisets https://api.dandiarchive.org ` from
157
- your local terminal. Note that if a dandiset with the same identifier as the one being imported
158
- already exists, that dandiset will not be imported.
159
-
160
- ```
161
- python manage.py import_dandisets [API_URL] --all --replace
162
- ```
163
-
164
- Same as the previous example, except if a dandiset with the same identifier as the one being imported
165
- already exists, the existing dandiset will be replaced with the one being imported.
166
-
167
- ```
168
- python manage.py import_dandisets [API_URL] --all --offset 100000
169
- ```
170
-
171
- This imports all dandisets (versions + metadata only, no assets) from the dandi-api deployment
172
- living at ` API_URL ` and offsets their identifiers by 100000. This is helpful if you want to import
173
- a dandiset that has the same identifier as one already in your database.
174
-
175
- ```
176
- python manage.py import_dandisets [API_URL] --identifier 000005
177
- ```
178
-
179
- This imports dandiset 000005 from ` API_URL ` into your local dev environment. Note that if there is already
180
- a dandiset with an identifier of 000005, nothing will happen. Use the --replace flag to have the script
181
- overwrite it instead if desired.
182
-
183
149
## Abbreviations
184
150
185
151
- DLP: Dataset Landing Page (e.g. https://dandiarchive.org/dandiset/000027 )
0 commit comments