codice / ddf-ui Goto Github PK

The version of usng.js needs to be bumped from 0.4.2 to 0.4.3

Federated source results do not show up in workspace lists because the query to retrieve list items adds a filter for the metacard-tag attribute. This attribute is not recognized by federated sources.

The Hour (00) does not display in correct format (12 Hours Standard). 12 Hour format should have a leading 0 for hours 1-9

Description

Most dropdowns do not open on Microsoft Edge with versions <= 44.18362.449.0

Steps to Reproduce

Open DDF on Microsoft Edge with one of the affected versions. Try to open the pan/zoom dropdown on the map or the location selection dropdown for an anyGeo search

Expected behavior :

A dropdown should open

Actual behavior:

No dropdown opens

Reproduces how often:

100%

Platform and environment:

Microsoft Edge versions <= 44.18362.449.0

Affects versions

2.19.x, master

Note: Issue migrated from DDF (codice/ddf#4656)

Description

Provide an issue that can be used to discuss the future of the module, aggregate related issues, maintenance, and work out a vision for the future of UI development and accompanying services.

Expected behavior:

Any effort that helps the UI be less coupled to DDF or provides insight to a stable, versionable API around DDF is welcome. See #4606 for initial ideas.

Alternatives include:

• Extracting just the JavaScript / UI itself to a separate repo, and versioning Intrigue's backend components themselves.

When exporting a result from the results list to csv, attributes that are blank/empty for the result still get copied over to the csv. It would be better to only include columns for which the record has an attribute value.

Description

If you have multiple 3D maps open and fill in a basic search form with a specific location, drawn lines and polygons are not rendered correctly across all maps. Point Radii and Bounding Boxes seem to work correctly.

Expected behavior

For all maps to display the drawings.

Screenshots

In the Inspector view, there are two different elements, both labeled "Actions". There should not be multiple different actions in the same view that are labeled the same thing.

Also, the lower "Actions" opens a drop down with Show, Arrange, etc. These options should be better exposed to the user rather than hiding in this dropdown.

Note: Migrated from DDF (codice/ddf#5428)

Description

Javadoc explains what components are, how they work at a behavior level (semantics), and helps the developer identify the important pieces they should care about when accomplishing a particular objective.

Version

N/A until progress starts.

Additional Information

Impacts: #123

Description

Fixes were made to usng.js and the version number in DDF needs to be updated.

Merged into 2.19.x codice/ddf#5827
needs a port to master

Note: Migrated from DDF (codice/ddf#4666)

Description

Normally in an OSGi environment, where a feature consists of many jars/bundles, going through the Maven project steps provides some degree of dependency protection. Culturally it also raises additional awareness and discipline because a project's larger-picture dependency graph directly impacts the potential for a clean build, parallel build, and an otherwise painless CI/CD experience.

For how classes are packaged within a Maven module, the impacts of a messy dependency graph are substantially less punishing, until the module needs to be split, or some other concern enters the picture.

Expected behavior:

Look into the current interpackage relationships within Catalog UI search, see what can easily be cleaned up, and then enforced at build time so the package dependencies stay clean.

Version

N/A until progress starts.

Additional Information

Impacts: #123

Might be worth looking into the following:
https://www.archunit.org/
https://blog.jdriven.com/2018/10/testing-the-architecture-archunit-in-practice/
http://www.mojohaus.org/extra-enforcer-rules/banCircularDependencies.html

If you draw a geometry over the anti-meridian (180 degrees longitude) on the 2D map, the shape changes to fit within the constraints of the map. Also, results that cross the anti-meridian aren't rendered over the anti-meridian; they change to fit within the constraints of the map. See examples below

Drawn geometries

Bounding Box (this change only occurs upon search/save)

Polygon (this change occurs immediately after the drawing is complete)

Line (also occurs immediately after drawing is complete)

Result geometries

Bounding Box
based on the result's location WKT, it should appear on the map like this:

but it's appearing here instead:

Polygon
should be:

but is:

Line
should be:

but is:

Description

When attempting to run a relative time query that is not wrapped in parentheses (like one built from a filter tree using cql.js), a parsing error occurs in cql.js. Wrapping queries in parentheses does not seem to be required at all (https://docs.geoserver.org/latest/en/user/filter/ecql_reference.html#filter-ecql-reference), so the cql parser should be adjusted to accept the query.

Affects versions

2.19.x, master

System and shared result forms with read-only permissions cannot be edited by a user. Shared read-only forms will display an error upon accessing the form and a user is unable to view which attributes are selected. For system forms a user can access the form and edit, however changes are not saved and a vague error is displayed.
Behavior should be consistent for read-only forms

There should be a null check here to prevent errors being thrown when the collection is empty

Currently, mousing over a thumbnail in the table view does not show the inspector icon (magnifying glass) in some situations. It does show up in the gallery view of the results in the side panel. This should be consistent with the gallery view, which shows the inspector icon and lets you click on it, opening the thumbnail in the new tab.

Currently, the user can only select a default Search Form. This functionality should be extended to result forms. If the user sets a default result form, that default should appear as the default in the Search Form builder, as well as the advanced and basic search forms.

No visualization indicator exists on the search form dropdown for the currently selected search form. This view could benefit from having a check mark on the selected form to inform the user.

Description:
A downstream project would like to override the filter input in queries.

Expected behavior (if applicable):
Nothing should change in DDF, the query panel should look exactly like it did before.

In https://github.com/codice/ddf-ui/blob/master/ui-frontend/packages/catalog-ui-search/src/main/webapp/component/query-adhoc/query-adhoc.view.js#L207 we are setting the cql without setting the filterTree.

This can cause issues elsewhere in the UI since the filterTree is now seen as the source of truth (sometimes?).

It's probably worth considering eliminating the cql attribute entirely so we aren't trying to keep filterTree and cql in sync, otherwise I can see us running into this issue more in the future.

When an IS EMPTY search is run, then edit the query back to the 'anyText' there is a console error and the field is deleted from the query entirely.

Currently, when creating a new result form, there is no default value selected. This presents the user with an non-valid error message. The form can't be submitted without selecting a value, so we should select the top one from the list as the default.

When manually entering USNG/MGRS coordinates for a bounding box, numbers have to be typed twice for them to show up in the field. This error will show up in the console:

Currently, if a user enters south and north values where south > north, the 2D map incorrectly renders a line. The 3D map takes all the coordinates into an array and renders a PolyLine (where coordinate order doesn't matter), so the correct bounding box is rendered. But both maps should not render anything since the bounding box is invalid.
If the search is executed with the invalid bounding box, it returns results within the intended bounding box because the search uses a polygon (where again, coordinate order doesn't matter). But with the recent UX changes to geo searches, we're moving more towards error handling being the responsibility of the user with an increase in specific inline errors. Therefore the search should be prevented from executing if the bounding box is invalid due to the south value being greater than the north value.

The 3D map does not delete the keyword geometries. If the user inputs a keyword, that geometry will show on the map. But if they input another keyword, the first geometry will remain, so two geometries will be showing. Only the second one should show.

In addition, for all geometries, making a geometry invalid (for example, deleting a coordinate) should make the geometry disappear on the map. instead the map continues to show the previously valid geometry.

No license header checks

We need to be able to configure additional tags for metacards that aren't complying with catalogue's access control

Description

If a user does not want to see a workspace or search/result form that has been shared with them anymore, they should be able to remove themselves from the sharing list.

Expected behavior:

User is allowed to remove themself

If an invalid value is entered into the easting field, both easting and northing fields will be cleared and vice versa. There should instead be an inline error message and the values should be retained so the user can edit what's already been entered.

log-sanitizer needs to be updated to a release version. (ui-backend/catalog-ui-search/pom.xml)

This is only a temporary workaround so that the repo can be ready for transition before the new release. Snapshot versions should not normally exist within this repo.

Resolve testing errors and re-enable the maven-frontend-plugin test execution

Note: Issue migrated from DDF (codice/ddf#4660)

Description

Remove the metacard edit endpoint. The patch service in Spark is being used instead.

Version

N/A until work is started.

Additional Information

Impacts: #123
Interested parties: @andrewkfiedler, @rzwiefel, @djblue

Add LGPL 3.0 License

See video below. The north field has the underscore placeholder automatically when switching from DD to DMS, the other fields get the placeholders after two or more decimal places are deleted from the DD coordinates. The underscores should be replaced with 0's.

Even without a visualization open the view takes a long time to switch between results.

At the moment we're relying on store within https://github.com/codice/ddf/blob/master/ui/packages/catalog-ui-search/src/main/webapp/component/metacard-overwrite/metacard-overwrite.view.js#L214. That makes it so the view will break on routes other than the workspace route. Instead, we should be using a passed in selectionInterface.

Currently, we force the Line geo to have a buffer. User should be able to search with a Line without having any buffer. If the Line does have a buffer, it should be at least 1 meter. This reflects how we treat Polygons.

When drawing bounding boxes in the DMS coordinate system, the fields aren't populated unless you switch to another coordinate system and switch back to DMS

When attempting to draw a point-radius or bounding box on the 3D map, the drawing stops after one click on the map

Innovation week work inspired by user conference suggestions. We would like to show the title and Preview text of files when a user clicks on a map marker in Intrigue.

Requirements:

• Preview Popups happen in both cesium and in openlayers.

Actions from the server currently can return with improper urls. We should be encoding them somewhere on the server. This can be recreated by making a source with a space in the name. If you do that, the client will hit an error when parsing the results with actions.

For some reason a lot of the text in the UI has turned black.