GSA / GSA/data.gov

SAP coordination: confirm SAP portal link destination and deep-link capability

Open
#6,051 0 comments 0 reactions 0 assignees View on GitHub
SAP
Dominant language
Python
Stars
1.1k
Forks
200
Avg merge
4h 56m
Merged PRs (30d)
5

Description

### What
In coordination with the SAP PMO, confirm the link destination for the application button in catalog.data.gov, and determine whether the SAP portal supports a deep-link or pre-filled application URL pattern.

### Why
The catalog UI implementation needs a confirmed, stable URL to link to. The answer also determines whether the pilot ships with a static link or a more useful pre-filled experience.

### Done When
- [ ] SAP PMO has provided a confirmed URL for the application link (landing page or application form)
- [ ] SAP PMO has confirmed whether a deep-link URL pattern is supported (e.g. passing a dataset identifier)
- [ ] SAP PMO has confirmed whether URL-parameter-based form pre-fill is supported
- [ ] Findings are documented and shared with the contractor team so the UI implementation ticket can be scoped correctly
- [ ] If deep-link or pre-fill is available, a sample URL pattern is documented with an example

### Notes
- This is a coordination and documentation task, not a build task
- Output feeds directly into the UI implementation ticket above
- If SAP cannot support deep-link or pre-fill for the pilot, static link is the fallback -- that is fine for phase one
- Sue owns the SAP PMO relationship; contractor team supports with technical questions as needed

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.