dspace-v6-api-dev

Files (3)

• SKILL.md
• openai.yaml · agents/
• rest-api.md · references/

SKILL.md (first lines)

# DSpace v6 API Dev

## Quick Start

- Confirm the target is DSpace 6.x with base path `/rest`.
- Read [references/rest-api.md](references/rest-api.md) before writing code, examples, or docs.
- Switch to `dspace-v6-db-structure` if the task is about tables, joins, or schema tracing.

## Working Rules

- Default to `Accept: application/json` unless XML is explicitly needed.
- Treat auth as cookie-based: `POST /login` returns `JSESSIONID`; reuse that cookie; invalidate with `POST /logout`.
- Address content objects by `uuid` (RFC 4122 string), not an integer id; DSpace 6.x is UUID-based. Resolve by handle via `/handle/{prefix}/{suffix}`. Registry schema/field ids stay integer.
- Check the endpoint family first, then the exact object shape from the reference.
- Use `limit` and `offset` on paginated endpoints; do not expect a total count.
- Use targeted `?expand=` values in real integrations; reserve `?expand=all` for inspection.
- Treat any write or restricted read as requiring a valid authenticated session.
- Prefer a minimal `curl` reproduction when behavior is unclear.

## High-Signal Notes

- `POST /items/{item id}/bitstreams?name=...` sends raw file bytes in the request body.
- `PUT /items/{item id}/metadata` replaces prior matching metadata entries.
- `PUT /bitstreams/{bitstream id}` updates metadata; `PUT /bitstreams/{bitstream id}/data` updates file content.
- `/status` returns `sourceVersion`/`apiVersion`, not a `token`; read auth state from the `JSESSIONID` cookie, not a response token.
- Shibboleth path naming in legacy docs is inconsistent; verify deployed config before implementing it.
- DSpace 6 documentation is legacy; do not reuse this skill for DSpace 7+.

## Bundled Resource

- [references/rest-api.md](references/rest-api.md): Endpoint map, session workflow, pagination rules, object skeletons, and source-derived caveats.

From prisma-ddti/skills, MIT.

More from prisma-ddti/skills