The moments that lead here
If one of these is your afternoon, you are in the right place.
Make accessioned collections discoverable in the discovery layer by embedding standardized descriptive fields.
2 ready prompts
Written for the moment this actually comes up.
Execute — do the immediate task
+Embed standardized descriptive fields into accessioned PDFs by adding headers with collection ID,…
Execute — do the immediate task
+Embed standardized descriptive fields into accessioned PDFs by adding headers with collection ID, title, and stable identifier, apply bates numbering that aligns with file names, and enable the Power Automate [workflow] to push metadata to the discovery layer this [deadline=month].
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Make accession PDFs discovery‑ready so cataloguers see consistent metadata: add a front matter…
Improve — make it easier to accept
+Make accession PDFs discovery‑ready so cataloguers see consistent metadata: add a front matter header with collection ID, title, creator, and persistent URL, align bates numbers with the file naming convention, and configure Power Automate to extract those fields into the discovery metadata [map]; test with [N=3] accessions before rollout.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Who does this, and with what
The same task is different work inside a different job.
Records ManagerAdobe Acrobat ProSharePointGoogle Drivealso: Map Fields to Discoveryalso: Validate Descriptive Fields
Next to this one
Other record work people do in Adobe Acrobat.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.