nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Document Properties: Title vs Name

jcarter

When I view a document's properties, the metadata (I'm just looking at the defaults) has both Title and Name. It appears both can be edited. What is the difference between these - how would one be used vs. the other?

Find more posts tagged with

Comments

steve

Hi,

It's exactly the same as with any document - for example a MS Word document.
A document has a Name - e.g. monkey.doc
And has a Title - e.g. Critically consider research into controlled and automatic processing.

Where a document type does not have a Title, we populate that field with the documents name.

Try it for yourself with a Word document and a TXT document…

Steve

jcarter

I think I understood that, but how are these intended to be used? It looks like Alfresco displays the Title in a user's space, not Name. I don't know if it is important, but currently my Word docs appear as 'title.doc' which is just the file name and they have an MSWord icon. If I change the Title to something more user friendly, the Word icon is replaced with a generic icon. Does this matter? If Alfrsco displays Title, how can Name be used?

Hi,

It's exactly the same as with any document - for example a MS Word document.
A document has a Name - e.g. monkey.doc
And has a Title - e.g. Critically consider research into controlled and automatic processing.

Where a document type does not have a Title, we populate that field with the documents name.

Try it for yourself with a Word document and a TXT document…

Steve

pvk

This double usage is still more confusing when it comes to space name : why should there be a difference between title and name in that context ?

The only explanation I could imagine is that the title would be dependent of the language and the name would not, as it couldbe used in script. Would that be a right explanation ?
In that case could a admin type of user enter a set of name depending on the language directly at the creation stage ?

frederick

If I change the Title to something more user friendly, the Word icon is replaced with a generic icon.

You must be changing the name then instead of the title, as file icons are guessed from the extension in the node name.

A good rule of thumb is that the title has a descriptive meaning, whereas the name has a functional meaning:

- names are used to construct the node QName, so duplicate names are not allowed in a space. This is important for e.g. CIFS.
- file icons are guessed from names, and when uploading content, the mimetype is also guessed from the name.

pvk

When it comes to that name vs title issue, my big concern is that it looks like the title is never used. When you navigate into spaces, what you see is always file names, not the titles you could expect to see displayed instead. The only way seems to develop a custom template for spaces.
Am I right ?

darko_narandzic

When it comes to that name vs title issue, my big concern is that it looks like the title is never used. When you navigate into spaces, what you see is always file names, not the titles you could expect to see displayed instead. The only way seems to develop a custom template for spaces.
Am I right ?

No. One can edit browse.jsp file to configure each view (icon view, details view, browse view).

davidd

if "Name" means "Filename", then why not call it "Filename"? It's confusing otherwise.