[MNT-9736] Search content by property using user's first and last names Created: 09-Oct-13  Updated: 01-Oct-19  Resolved: 22-Jul-16

Status: Closed
Project: Service Packs and Hot Fixes
Component/s: Share Application
Affects Version/s: 4.1.5
Fix Version/s: None

Type: Improvement
Reporter: Craig Tan Assignee: Closed Issues
Resolution: Won't Fix Votes: 1
Labels: ENHCleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Search_First_Last_Name.png     PNG File Search_Result_First_Last_Name.png    
Issue Links:
Dependency
Depends on SHA-1617 Search by display name Closed
Related
relates to ALF-18744 Search by property for content doesn'... Closed
ACT Numbers:

00136749

Premier Customer:
Yes

 Description   

Currently each document contains three fields namely cm:creator, cm:modifier and cm:owner that contains usernames and not first name and last name, so when you do a search for documents created / modified by a person, you will need to type in their username, but people don't often know other people's usernames. They only know their names, but this is not indexed since the fields only contain their usernames.

We would like to leave the design to the Alfresco engineering team, but we have one suggestion for your to consider:

Alfresco may like to consider introducing a new aspect that contains 3 new properties:

creatorName
modifierName
ownerName

and people can decide whether they want to apply the aspect to their contents or not (by default it's not applied). It is a bit like the 'Versionable' aspect.

If the aspect is applied to a content, these fields will contain people's names (eg. First name + Last name) and Alfresco will make sure that when you upload a document or make changes to a document or folder, these fields are updated with the person's name accordingly, again, a bit like the 'Versionable aspect', which is behavior aware.

The design may also need to take care of how Alfresco will do updates on existing documents and folders already in the repository with these new properties retrospectively.



 Comments   
Comment by Craig Tan [ 18-Oct-13 ]

This problem is a little worse from a UX perspective than outlined here. The problem is that in ALL search results the display name is shown, but when a user enters a search this is not searched NOT EVEN the userid, even though this is indexed. As part of UX design you should never display any property or data to a user that they can't search for. Normaly users won't know that this data is not being searched and will assume that the document has been found because it matches the user.

If I enter this search: (see Search_First_Last_Name.png)

and then I see this result: (see Search_Result_First_Last_Name.png)

My immediate belief is that it has been found because it was modified by David Bird, whereas it has in fact been found because David is in the content.

Suggestions: either include the modifier is the properties searched or remove "modified by" from the result set.

Generated at Thu Jul 09 10:10:15 BST 2020 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.