In the Liquid State platform, are document-level and page-level tags the same as one-another? Or are they separate tags?
→ They’re seperate tagsIf I tag both a document and a page with "abc", is there one tag in the back-end that relates to both the document and page? Or are there two tags: one "abc' at the document-level, and another "abc" at the page-level?
→ They’re seperate as well. On each document and on each page - the tags are seperate.Are tag case sensitive? i.e., are "abc" and "ABC" considered to be the same tag or different tags?
→ Yes the tags are case sensitive, they are different tagsWithin the JSON for a document or page's metadata, the tag entered via the CE UI always seems to include two fields: Label and Term, their values seem to always be exactly the same.
Is there any difference between these two fields, and would you recommend using one or the other as the source of truth for tags in DocHub?
→ ‘Label' is supposed to be a human readable term for the tag, and ‘Term’ is supposed to be for the programmatic systems to read and confirm that the same tag is being used. So the source of truth should be ‘Term’. This should help with programmatic updates for documents. To simplify the UI of Carbon - we treat the ‘Term’ and 'Label’ as the same.There is a field that sometimes appears within the metadata: scheme. I noticed that although there is an area for this when you are viewing tags in the CE UI, it is always empty.
By creating a tag via the CE UI, the scheme field is not included in the metadata JSON for that document/page. If you create a tag in Ubiquity, the scheme field is included in JSON but is empty.
Is this feature current/relevant? Would you recommend including it in our design or ignoring it?
→ Just like ‘Label’ is supposed to be for human reading and ‘Term’ is for programmatic system to read the tag, ‘Scheme’ is for content management to set a specific meaning for the tags. This is only to be used if your system design has a need for it. This would only be applicable for Programatic updates and for the sake of simplicity CE UI doesn’t account for it. If you do not have a need for ‘Scheme’ - you should ignore it.Are the fields within document-level readonly metadata always the same?
→ Yes, they are generally the same. It is possible we would add new fields as the system grows but the fields already there won’t be removed or have their change of meaning. If a new field is added - it will depend on case per case basis how it impacts the metadata and we would inform you of the same.Are the fields within page-level readonly metadata always the same?
→ Yes, they are generally the same. It is possible we would add new fields as the system grows but the fields already there won’t be removed or have their change of meaning. If a new field is added - it will depend on case per case basis how it impacts the metadata and we would inform you of the same.Is it possible to link to an automated document rather than a page within a document?
→ No, while you can publish the automated document and then link to the first page where the users could scroll through, you can’t automatically create a table of contents and link to a page within a document.Is line breaks to paragraph fields supported in Carbon Editor?
→ No, Carbon editor is not a html editor, adding line breaks to paragraph fields is not supported, each paragraph should be a single <p> tag and simple styling applied through the editor controls, not through editing the html directly. These limitations are essential for us to support the multiple export formats that we do by limiting the structure of the input in the first place.
Potential issues -Adding links in tables and lists using ckeditor
Manage space
Manage content
Integrations