onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

cap-media

Media handling with nothing but core CDS: a LargeBinary element annotated with @Core.MediaType, @Core.IsMediaType and @Core.ContentDisposition, uploaded from a UI5 UploadSet.

The route before @cap-js/attachments existed and still the one to read when you want the mechanism rather than the plugin — the entity carries content, mediaType, fileName and size itself, the service is a plain projection, and a before-CREATE handler writes the /content URL the UI needs back onto the record.

GitHub7 ★

Facts

Last push

Where it sits

Lives in
CAP
Demonstrates
AttachmentsCAPAttachmentscapabilityStoring a file somebody uploaded next to the record it belongs to, and getting it back out — where the bytes actually live, who may read them, and what the UI shows while they are being scanned.

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained

As a sample

Form
does not say

Connections1

Download
cap-media connectionscap-mediaPROVIDES→ demonstrates1demonstrates authoredAttachments

README

quoted from miyasuta/cap-media, read
miyasuta/cap-media/README.mdOn GitHub

Getting Started

Welcome to your new project.

It contains these folders and files, following our recommended project layout:

File or FolderPurpose
app/content for UI frontends goes here
db/your domain models and data go here
srv/your service models and code go here
package.jsonproject metadata and configuration
readme.mdthis getting started guide
excerpt, no licence read, read the rest, on GitHub

Details

Sources3
GitHub APIdiscovered here, miyasutachecked
github.com/miyasuta/cap-mediatree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domaincap, data-and-persistence
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-cap-media
JSON
/artifacts/miyasuta-cap-media.json
MCP
Connecting an agent