I need to associate a large number of documents with a polygon feature layer published in Portal. The goal is for users to click on a polygon and see a pop-up containing a field with a URL. Clicking this URL should open a document library in SharePoint that contains all the documents associated with the polygon.
The documents and polygons share a common ID, which can be used as the link between them. However, I am unsure how to configure this mechanism in Portal or how best to set up the integration with SharePoint.
After investigating the Parcel Fabric Data Model, I’ve determined it is not suitable for this situation or the desired functionality.
Does anyone have recommendations or examples of how to configure this setup in Portal? Any advice on integrating SharePoint document libraries with feature layer attributes would also be appreciated.
I have accomplished this one way using SharePoint and seen another way possible at our local County Assessor's office.
SharePoint Method
Adding a field to the feature layer named something like "RelatedDocumentURL" or something like that will allow you to paste in a url for the SharePoint directory containing the related documents. I would ensure that the link to the directory was modified so that users accessing that only had permission to view documents. Otherwise, they end up getting prompted for a login, which fails. After adding these urls to the field for each feature, a popup can display that field value as a hyperlink in various ways.
If adding individual links to each parcel sounds nearly impossible...
Alternative Method
A custom web application that allows navigation by parcel number should be developed. This requires the documents to be stored in a way that is either retrievable from a database or from a web accessible repository by parcel number. Then, in the popups for the parcel layer, you create an attribute expression that builds a url like: var url = "https://domainname.com/" + $feature.parcel_number. Then, add that attribute expression to popups according to the previously linked documentation.
Neither of these methods is easier. Both require that the documents be indexed somehow. I feel like the Alternative Method puts the work of organizing documents and providing means of displaying them back in the court of the assessors and clerks and allows GIS admins/analysts to provide a means of referencing them instead of doing much of the job of someone in another role.
What do you mean by saying "The documents and polygons share a common ID"? the key is to get the map from ID and document URL. then you can create a related table in your enterprise Geodatabase. This is static though.
It will be tricky to have a seamless system integration, still possible if you can infer the document url from the ID.