You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Entry - owner (group or department), not necessarily Entry_owner attribute though

posted on April 8, 2019 Show version history

Our city's repository at this time is a mass of archived city documents that cover the Planning Department, Building Dept, Board of Health, HR and Engineering departments and soon to have a couple more departments added in as well.

IT (me) is a player in managing the structure and integrity of the entries, but we are putting the task of managing each department's entries on their staff.

Originally, we had one template in use for each department, but as more entries and files and have come in the best practice turned out for most of the entries to have our Property Template applied to them to capture their metadata because that template captures down to the parcel id/street address and unit # point attribute; this template helps the end users (public and internal) search easily for a specific place to return their intended entries.

This has however made the Property Template be used by multiple departments.

 

  • I want a way to easily identify which department an end user should contact if they need more help on an entry or if they find an error that needs to be corrected.

 

What are the hive mind thoughts on how to address the best way to show who 'owns'/manages/maintains the entry to the department level? 

I would love to be able to assign the native "Entry Owner" to the User Group as that would make the most sense, but it does not seem like that is possible? 

Seems like a general metadata field applied to all template of something like "Department to Contact" might be the easier way to handle this, but I would love to hear from any and all of you out there who might have dealt with this issue.

 

We are on Rio 10.3, self hosted, most users are still on the desk client with web link coming out very soon.

 

edit: I have read many of the posts here in the community that are available regarding ownership and creator level attribute but none of them seemed to address what I am expecting.

0 0
replied on April 11, 2019

Rob, thank you very much! That is what I was envisioning, and we do use AD so that is a perfect automatic addition, thank you for that idea!

0 0
replied on April 9, 2019

I think using a read-only metadata field is the best path forward. When a document is submitted, WF uses the Find Group activity to determine the user's department (this assumes that your system has the appropriate LF or AD groups configured for each department) and applies that value to the read-only Department to Contact field.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.