Date: Fri, 29 Mar 2024 11:49:09 -0400 (EDT) Message-ID: <2013297855.299.1711727349610@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_298_174141158.1711727349610" ------=_Part_298_174141158.1711727349610 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Esme created a Github label to draw attention to the External Content pr=
oblem.
Daniel Lamb brought up 'Redirect Content' as a potential solution for Isla=
ndora, although a smart client would be required to provide Authorization h=
eaders as the redirect responses are followed. Bypassing the 'Redirec=
t Content' altogether and simply providing public URIs to binaries while ne=
ver creating LDPNRs would not suffice, as it would prevent API-X from being=
utilized.
During the discussion of External Content, Simeon brought to light that = we may be creating different classes of content that have different behavio= urs, and that's not the easiest to specify. For example, external con= tent could be downloaded immediately and then ingested into the system.&nbs= p; It could not be downloaded and just referenced when needed, with Fedora = acting as a proxy. For example, we've just required that checksums MU= ST be provided on a HEAD request, but that could be potentially very expens= ive for an implementation whose content is stored externally on S3. S= o how do we, from an API point of view, clarify between different types of = 'External Content', if at all. In particular, if we do, then are we t= ruly creating LDPNRs? We may be trying to have our cake and eat it to= o.
Ben Armintor would like to use the Content-Location header instead of me=
ssage/external-body in a Content-Type header. It may be useful for pe=
ople to look at the difference between the two.
Esme Cowles made a proposal at the end of the meeting and is writing it up=
. It will be published at ht=
tps://github.com/fcrepo/fcrepo-specification/wiki/External-Content .