Timeline for When are TCM URIs "managed?"
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 28, 2017 at 17:15 | comment | added | Rick Pannekoek | Yeah, managed links to Categories in custom content/metadata are a weird beast; the UI doesn't support them, but the CM Kernel does allow them (AFAIR, we had some taxonomy publishing use case in mind that was never actually implemented). Indeed, storing TCM URIs in text fields does not result in managed links. | |
| Apr 28, 2017 at 15:01 | comment | added | Alvin Reyes | In terms of XLinks to Categories, I know we can select Categories in Schema definitions (for selections for a given text field). But could you choose/insert Category TCM URIs anywhere and have the CM Kernal manage them? I'm thinking of Bart's Item Selector extension, which stores TCM URIs as strings (and wouldn't be content portable), right? | |
| Apr 28, 2017 at 15:00 | comment | added | Alvin Reyes | It might indeed have been TCM URIs in App Data. I think this was around the same time Content Porter started having the options to include App Data (which I can't remember if they appeared at the same time as App Data or shortly after). | |
| Apr 28, 2017 at 14:53 | vote | accept | Alvin Reyes | ||
| Apr 26, 2017 at 18:59 | history | answered | Rick Pannekoek | CC BY-SA 3.0 |