You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 5, 2021. It is now read-only.
At DOJ we are using a SharePoint solution that is not feature-rich when it comes to character level text processing. We are collecting code.json entries using an embedded forms feature in SharePoint, but we have limited ability to do anything that SharePoint doesn't provide some sort of plug in for. There is no readily available scripting tool within our reach to manage logic.
Because of that we have allocated a certain number of fields to various array values like keyword, language and so forth. So we have room on the UI for up to 5 keywords, and if a user only fills three of those blanks, the json file will have two null fields (,"") . This causes the harvester to post blank values, little null icons where the key words would be displayed. Its my thinking that a smarter harvester, one that discards null fields, would be a better investment than 10 - 15 improved json generating tools across the government that all will need to have logic that strips null fields.
The text was updated successfully, but these errors were encountered:
At DOJ we are using a SharePoint solution that is not feature-rich when it comes to character level text processing. We are collecting code.json entries using an embedded forms feature in SharePoint, but we have limited ability to do anything that SharePoint doesn't provide some sort of plug in for. There is no readily available scripting tool within our reach to manage logic.
Because of that we have allocated a certain number of fields to various array values like keyword, language and so forth. So we have room on the UI for up to 5 keywords, and if a user only fills three of those blanks, the json file will have two null fields (,"") . This causes the harvester to post blank values, little null icons where the key words would be displayed. Its my thinking that a smarter harvester, one that discards null fields, would be a better investment than 10 - 15 improved json generating tools across the government that all will need to have logic that strips null fields.
The text was updated successfully, but these errors were encountered: