«unknown» (2022-04-12)
Requirements:
- As a user, I want the registry loader tools to continue after the ingestion of a product fails #253
- Simplify the readme and procedure to start the registry with docker-compose #241
- As a user, I want to switch a bundle and it's associated collections and products from a protected status to operational. #224
- As a user, I want to change the archive status for a collection and it's associated products #223
- As a developer, I want to be able to access the registry related docker images from https://hub.docker.com/ #187
Improvements:
- Make CICD work on registry-api repository #260
- Simple wrappers to call the pds-batch-loader and pds-service-loader docker compose services #257
- Update the README of the harvest service repositories #245 [s.high]
- As a developer, I want to update and run the integration tests from the 'registry' repository #230
Other closed issues:
- test registry docker compose with opensearch instead of elasticsearch #250
- Update docker-compose profiles to match developer use case #225
- As a developer I want to start the registry with a single command #208
v1.1.0-SNAPSHOT (2022-02-07)
Requirements:
- As a user, I want to be able to ingest a set of files specified in a file listing #201
- As a user, I want big data ingestion tools packaged and dockerized together #200
Improvements:
- Rename bigdata repositories #237
Defects:
Other closed issues:
- Tag new version of registry-common, registry-mgr, supplementer, harvest, and parent registry-app to resolve log4j vulnerability #232
- Develop design documentation for staging vs production data for review with SWG #228
- Document big data harvest / registry manager / crawler installation and operation #218
v1.0.3 (2022-01-11)
Requirements:
- As a developer, I want to deploy the registry with a single docker-compose command #186
- As a user, I want the registry app components to be able to ingest data sets containing 1+ million products #179
Defects:
- the snapshot releases are not created for big-data-harvest-client #231 [s.critical]
- harvest flags as mandatory a config elements the docs describe as optional #220 [s.low]
Other closed issues:
- Implement docker-compose for registry components #216
- Dockerize Harvest and Registry Manager as a single image #214
- Build Scalable Harvest #196
v1.0.2 (2021-12-10)
Other closed issues:
- Clearly define best practices configuration for harvest/registry-mgr #217
v1.0.1 (2021-12-10)
Improvements:
- Develop cost model and reporting for Registry deployments #90
Defects:
- Harvest network I/O errors can cause corrupted JSON #205 [s.high]
- stable continuous integration don't generate the packages tar.gz and .zip properly. #177 [s.medium]
Other closed issues:
- Build Harvest Client #198
- Build scalable file system crawler #197
- Big Data Harvest analysis / POC #195
- Deploy IMG Registry in AWS #88
- Deploy GEO Registry in AWS #87
v1.0.0 (2021-10-04)
Requirements:
- As a user, I want to know the version of all registry app components via the command-line #185
- As a node operator, I want to harvest and ingest a subset of a bundle based on existing registered data. #130
- As a registry user, I want to ingest supplemental metadata from Product_Metadata_Supplemental. #12
Improvements:
- Upgrade API on AWS with latest version 0.3.1 #173
Defects:
- docker instructions in README.md are not working #163 [s.medium]
- Harvest does not work with registry manager #2
Other closed issues:
- Create new app to load supplemental metadata into registry #172
- Change Harvest to store list of supplemental products in a file #171
- terraform Fargate deployment of registry api service #166
v0.3.2 (2021-07-01)
Requirements:
- As a manager, I want the registry to have regression tests included in CI #154
- As a developer, I want to extend the registry-mgr and harvest using the Java API #153
- As a node operator, I want the the registry schema to update autonomously when new data is ingested. #146
- As a node operator, I want to ingest metadata regarding secondary products that belong to a collection. #143
Improvements:
- Initial deployment of API on AWS - Fargate solution #165
- Develop plan for instituting AWS ES Cross Cluster Search #150
Defects:
Other closed issues:
- Deploy latest version of pds-registry-app to pds-gamma #167
v0.3.1 (2021-05-07)
Requirements:
- The service shall provide a staging capability for artifacts staged for release #65
- The service shall require user authorization for updating registry metadata #66
- The service shall require checksums as metadata for registry artifact to enable system-wide integrity checking #68
- The service shall allow for queries for registered artifacts #55
- The service shall allow deletion of registered artifacts #70
- The service shall allow updates to registered artifacts #71
- The service shall store metadata for a registered artifact in an underlying metadata store #72
- The service shall require a logical identifier and version be provided for all registered artifacts #73
- The service shall assign a global unique identifier to a registered artifact #56
- The service shall accept metadata for a registered artifact in a defined format #75
- The service shall maintain configuration regarding the classes of artifacts to be registered #59
- The service shall provide a means identifying relationships between artifact registrations #58
- The service shall accept artifact registrations. #57
Improvements:
- Update Registry App landing page to divert data users to separate landing page for using the PDS API #158
Other closed issues:
- Work w/ SAs to define production deployment strategy in AWS #159
- Employ budget alerts and if possible, rate/egress limits on AWS services #151
- Perform trade study and implement revised version of attribute search #60
v0.3.0 (2021-04-19)
Requirements:
- As a node operator, I want to be able to tag ingested data with the node it is ingested by. #147
- As a developer, I want to include supplemental file data sizes in the registry #145
- As a node operator, I want to ingest metadata regarding secondary collections that belong to a bundle. #144
- As a node operator, I want actionable, user-friendly error messages for registry schema failures #142
- As a manager, I want a cost model for deploying a registry + API in AWS #141
Improvements:
- Verify pds-registry-app doc is up to date, have registry configuration in the harvest conf examples #133
- Develop ElasticSearch client library to be utilized by harvest / registry-mgr #131
- Create a registry docker for developer testing #129
- load data for kibana test #127
- analyze need, propose architecture #125
- Update registry-mgr documentation as stated in #86 #123
- Develop kibana configuration for EN registry UI #120
- Manage product relationships v2 - collection inventories #114
- Have pds4 properties syntax match the syntax decided for the PDS API #113
- Update Registry API per PDS API v0-beta #92
Defects:
- docker build is version locked #135 [s.medium]
- Make example harvest configuration more explicit #112 [s.high]
- Test data in pds-registry-app-0.2.2-bin.zip is missing data products. #110 [s.high]
Other closed issues:
- As a manager, I want to understand the distinct types of data contained within the archive #134
- Install a test registry and kibana #121
- Test registry-app multi-node deployment #118
- Update collection products with parent bundle reference #116
- Parse collection inventories and add parent collection reference to products #115
- Deploy Registries in AWS #91
- Deploy EN Registry in AWS #86
- Registry Integration component #81
- Update pds-registry-app to use new pds-registry-mgr-elastic #40
v0.2.4 (2021-01-05)
Requirements:
- The service shall require a subset of file system metadata in order to support data metrics generation #67
Improvements:
Defects:
Other closed issues:
- Manage relationships between bundles / collections / products #76
- Integrate Registry API into pds-registry-app #42
v0.2.3 (2020-12-21)
0.2.3 (2020-12-21)
Improvements:
- Add the API to the pds-registry-app package, with documentation #102
Defects:
- harvest and registry manager in pds-registry-app-0.2.2-bin.zip are missing batch scripts for windows #108 [s.medium]
- Issues with Registry App Documentation #106
Other closed issues:
- Manage relationships described by reference types #77
v0.2.2 (2020-12-03)
Improvements:
- update registry-manager load-data to handle additional use cases #103
- Beta test operational deployment #13
Defects:
- Broken link in pds-registry-app docs #104
Other closed issues:
- Develop a version 0 API connected to ElasticSearch registry #99
- Research RDF technologies to handle pds4 label cross-references in the registry #97
- Retrofit pds-registry-app CI to use roundup-action #94
- Document performance benchmarks in registry app docs #85
- Develop test plan #82
- Improve Attribute Search Component #53
0.2.1 (2020-10-30)
Other closed issues:
- Research tech stack modifications due to large number of search fields in registry #93
0.2.0 (2020-10-27)
Other closed issues:
- Update the release package to integrate the new registry mgr repository #98
0.3.0 (2020-10-27)
Improvements:
- Have a blob store in Elastic Registry for pds labels #44
- Refactor Registry Manager and Harvest to use ElasticSearch tech stack #37
Defects:
- Fix the Json data dictionary format #64
Other closed issues:
- Complete documentation for dynamic schema management #95
- Download large data set for testing #84
- Deploy and install multi-node ES #83
- Update the index schema in ES dynamically when new record are ingested #61
- Validate Elastic Search index configuration for attribute search #45
- Update Registry App documentation per ES refactor #43
- Tag pds-registry-app for last Solr build #39
0.1.2 (2020-08-13)
Improvements:
- Complete revised trade study on Solr vs ElasticSearch #38
- Analyse migration cost vs visualization tool benefit if we use elasticSearch/Kibana (instead of solr/banana) #35
- Design and document Registry cluster expansion approach #30
- Enhance documentation for PDS4 Attribute Search deployment and customization #22
- Develop ability to deploy Test vs Operations Registry environments #15
- Develop Registry reporting / visualization component #11
- Develop capability for handling multiple product versions #10
- Design and implement Security and Authorization component #9
- Design and implement Multi-Node Deployment capability #8
- Design and Implement capability to handle archive_status #16
Other closed issues:
- Research and document Application Security #29
- Research and document Server Security #28
- Update documentation with different options for sharding and multiple nodes #24
v0.1.1 (2020-05-22)
Improvements:
- Update Schema Generator for handling special cases where ancestor classes are needed #20
- Develop Customization capability for PDS4 Attribute Search #7
- Develop PDS4 Attribute Search capability #6
Defects:
- Unable to build application due to file size limit #21
- registry installation's documentation may be insufficient #5
- pds-app-registry doesn't build on Windows #3
0.1.0 (2020-03-31)
nightly (2020-03-11)
* This Changelog was automatically generated by github_changelog_generator