|
1 | 1 | ## Overview
|
2 | 2 | These are not the release notes, which can be found https://github.com/NASA-IMPACT/COSMOS/releases. Instead, this is a changelog that developers use to log key changes to the codebase with each pull request.
|
3 | 3 |
|
| 4 | +## What to Include |
| 5 | +For each PR made, an entry should be added to this changelog. It should contain |
| 6 | +- a brief description of the deliverable of the feature or bugfix |
| 7 | +- exact listing of key changes such as: |
| 8 | + - API endpoint modified |
| 9 | + - frontend components added |
| 10 | + - model updates |
| 11 | + - deployment changes needed on the servers |
| 12 | + - etc. |
| 13 | + |
4 | 14 | ## Changelog
|
5 |
| -### 1182-ml-classification-queue |
6 |
| -#### Features |
7 |
| -- |
8 |
| -#### Deployment Changes |
9 |
| -- a new env value has been created called `INFERENCE_API_URL` |
| 15 | +- 1182-ml-classification-queue |
| 16 | + - Changes: |
| 17 | + - a new env value has been created called `INFERENCE_API_URL` |
| 18 | + |
| 19 | +- 1052-update-cosmos-to-create-jobs-for-scrapers-and-indexers |
| 20 | + - Description: The original automation set up to generate the scrapers and indexers automatically based on a collection workflow status change needed to be updated to more accurately reflect the curation workflow. It would also be good to generate the jobs during this process to streamline the same. |
| 21 | + - Changes: |
| 22 | + - Updated function nomenclature. Scrapers are Sinequa connector configurations that are used to scrape all the URLs prior to curation. Indexers are Sienqua connector configurations that are used to scrape the URLs post to curation, which would be used to index content on production. Jobs are used to trigger the connectors which are included as parts of joblists. |
| 23 | + - Parameterized the convert_template_to_job method to include the job_source to streamline the value added to the `<Collection>` tag in the job XML. |
| 24 | + - Updated the fields that are pertinenet to transfer from a scraper to an indexer. Also added a third level of XML processing to facilitate the same. |
| 25 | + - scraper_template.xml and indexer_template.xml now contains the templates used for the respective configuration generation. |
| 26 | + - Deleted the redundant webcrawler_initial_crawl.xml file. |
| 27 | + - Added and updated tests on workflow status triggers. |
| 28 | + |
| 29 | +- 2889-serialize-the-tdamm-tags |
| 30 | + - Description: Have TDAMM serialzed in a specific way and exposed via the Curated URLs API to be consumed into SDE Test/Prod |
| 31 | + - Changes: |
| 32 | + - Changed `get_tdamm_tag` method in the `CuratedURLAPISerializer` to process the TDAMM tags and pass them to the API endpoint |
| 33 | + |
| 34 | +- 960-notifications-add-a-dropdown-with-options-on-the-feedback-form |
| 35 | + - Description: Generate an API endpoint and publish all the dropdown options necessary as a list for LRM to consume it. |
| 36 | + - Changes: |
| 37 | + - Created a new model `FeedbackFormDropdown` |
| 38 | + - Added the migration file |
| 39 | + - Added the `dropdown_option` field to the `Feedback` model |
| 40 | + - Updated the slack notification structure by adding the dropdown option text |
| 41 | + - Created a new serializer called `FeedbackFormDropdownSerializer` |
| 42 | + - Added a new API endpoint `feedback-form-dropdown-options-api/` where the list is going to be accesible |
| 43 | + - Added a list view called `FeedbackFormDropdownListView` |
| 44 | + - Added tests |
| 45 | + |
| 46 | +- 1217-add-data-validation-to-the-feedback-form-api-to-restrict-html-content |
| 47 | + - Description: The feedback form API does not currently have any form of data validation on the backend which makes it easy for the user with the endpoint to send in data with html tags. We need to have a validation scheme on the backend to protect this from happening. |
| 48 | + - Changes: |
| 49 | + - Defined a class `HTMLFreeCharField` which inherits `serializers.CharField` |
| 50 | + - Used regex to catch any HTML content comming in as an input to form fields |
| 51 | + - Called this class within the serializer for necessary fields |
| 52 | + |
| 53 | +- 1030-resolve-0-value-document-type-in-nasa_science |
| 54 | + - Description: Around 2000 of the docs coming out of the COSMOS api for nasa_science have a doc type value of 0. |
| 55 | + - Changes: |
| 56 | + - Added `obj.document_type != 0` as a condition in the `get_document_type` method within the `CuratedURLAPISerializer` |
| 57 | + |
| 58 | +- 1014-add-logs-when-importing-urls-so-we-know-how-many-were-expected-how-many-succeeded-and-how-many-failed |
| 59 | + - Description: When URLs of a given collection are imported into COSMOS, a Slack notification is sent. This notification includes the name of the collection imported,count of the existing curated URLs, total URLs count as per the server, URLs successfully imported from the server, delta URLs identified and delta URLs marked for deletion. |
| 60 | + - Changes: |
| 61 | + - The get_full_texts() function in sde_collections/sinequa_api.py is updated to yeild total_count along with rows. |
| 62 | + - fetch_and_replace_full_text() function in sde_collections/tasks.py captures the total_server_count and triggers send_detailed_import_notification(). |
| 63 | + - Added a function send_detailed_import_notification() in sde_collections/utils/slack_utils.py to structure the notification to be sent. |
| 64 | + - Updated the associated tests effected due to inclusion of this functionality. |
| 65 | + |
| 66 | +- 3228-bugfix-preserve-scroll-position--document-type-selection-behavior-on-individual-urls |
| 67 | + - Description: Upon selecting a document type on any individual URL, the page refreshes and returns to the top. This is not necessarily a bug but an inconvenience, especially when working at the bottom of the page. Fix the JS code. |
| 68 | + - Changes: |
| 69 | + - Added a constant `scrollPosition` within `postDocumentTypePatterns` to store the y coordinate postion on the page |
| 70 | + - Modified the ajax relaod to navigate to this position upon posting/saving the document type changes. |
| 71 | + |
| 72 | +- 3227-bugfix-title-patterns-selecting-multi-url-pattern-does-nothing |
| 73 | + - Description: When selecting options from the match pattern type filter, the system does not filter the results as expected. Instead of displaying only the chosen variety of patterns, it continues to show all patterns. |
| 74 | + - Changes: |
| 75 | + - In `title_patterns_table` definition, corrected the column reference |
| 76 | + - Made `match_pattern_type` searchable |
| 77 | + - Corrected the column references and made code consistent on all the other tables, i.e., `exclude_patterns_table`, `include_patterns_table`, `division_patterns_table` and `document_type_patterns_table` |
| 78 | + |
| 79 | +- 1190-add-tests-for-job-generation-pipeline |
| 80 | + - Description: Tests have been added to enhance coverage for the config and job creation pipeline, alongside comprehensive tests for XML processing. |
| 81 | + - Changes: |
| 82 | + - Added config_generation/tests/test_config_generation_pipeline.py which tests the config and job generation pipeline, ensuring all components interact correctly |
| 83 | + - config_generation/tests/test_db_to_xml.py is updated to include comprehensive tests for XML Processing |
| 84 | + |
| 85 | +- 1001-tests-for-critical-functionalities |
| 86 | + - Description: Critical functionalities have been identified and listed, and critical areas lacking tests listed |
| 87 | + - Changes: |
| 88 | + - Integrated coverage.py as an indicative tool in the workflow for automated coverage reports on PRs, with separate display from test results. |
| 89 | + - Introduced docs/architecture-decisions/testing_strategy.md, which includes the coverage report, lists critical areas, and specifically identifies those critical areas that are untested or under-tested. |
| 90 | + |
| 91 | +- 1192-finalize-the-infrastructure-for-frontend-testing |
| 92 | + - Description: Set up comprehensive frontend testing infrastructure using Selenium WebDriver with Chrome, establishing a foundation for automated UI testing. |
| 93 | + - Changes: |
| 94 | + - Added Selenium testing dependency to `requirements/local.txt` |
| 95 | + - Updated Dockerfile to support Chrome and ChromeDriver |
| 96 | + - Created BaseTestCase and AuthenticationMixin for reusable test components |
| 97 | + - Implemented core authentication test suite |
| 98 | + |
| 99 | +- 1195-implement-unit-test-for-forms-on-the-frontend |
| 100 | + - Description: Implemented comprehensive frontend test suite covering authentication, collection management, search functionality, and pattern application forms. |
| 101 | + - Changes: |
| 102 | + - Added tests for authentication flows |
| 103 | + - Implemented collection display and data table tests |
| 104 | + - Added universal search functionality tests |
| 105 | + - Created search pane filter tests |
| 106 | + - Added pattern application form tests with validation checks |
0 commit comments