Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quarterly report - 2024Q4 #22

Closed
mbjones opened this issue Jun 12, 2024 · 1 comment
Closed

Quarterly report - 2024Q4 #22

mbjones opened this issue Jun 12, 2024 · 1 comment
Assignees
Labels
A1-2.4 Exhibit A1 - 2.4 D-1.4 Progress Reports (Quarterly, Annually) ⚙️ Task Non-coding work item mgmt

Comments

@mbjones
Copy link
Member

mbjones commented Jun 12, 2024

Quarterly report, 2024Q4

@mbjones mbjones added the D-1.4 Progress Reports (Quarterly, Annually) label Jun 12, 2024
@mbjones mbjones self-assigned this Jun 12, 2024
@mbjones mbjones changed the title Quarterly report - $QUARTER Quarterly report - 2024Q4 Jun 12, 2024
@mbjones mbjones moved this to Backlog in VegBank Project Jun 12, 2024
@regetz regetz assigned regetz and unassigned mbjones Oct 4, 2024
@regetz regetz added A1-2.4 Exhibit A1 - 2.4 ⚙️ Task Non-coding work item mgmt labels Nov 22, 2024
@regetz
Copy link

regetz commented Feb 5, 2025

Reporting Period: 2024-10-01 - 2024-12-31

Highlights:

  • Completed full load of the existing VegBank database into the new database system in the Development environment, for use in API development and testing. Completed end-to-end documentation of the process, for use when completing the future rollout to Production.
  • Formalized core API resource types (e.g. plot observations, taxon observations, community classifications, plant and community concepts, projects, references, etc), and designed and documented basic request and response schemas for these resources.
  • Identified candidate approaches for handling bulk uploads of resources (e.g., plot observations), with different strategies for determining how existing vs new dependent entities (e.g., parties and projects) are recognized and handled at load time.
  • Evaluated and selected the software framework for API implementation, completed a rapid prototype with basic query functionality against a local test instance of the database, and began work to containerize the API engine for deployment in the hosted cluster environment (Development and Production).
  • Obtained and reviewed a second sample of California vegetation plot data from VegCAMP, with samples from reconnaissance and accuracy assessment surveys.
  • Continued initial exploration of California data to understand similarities and differences with the VegBank schema, as needed to begin eventual implementation of a data ingest workflow.

Issues:

@regetz regetz closed this as completed Feb 5, 2025
@github-project-automation github-project-automation bot moved this from Backlog to Done in VegBank Project Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A1-2.4 Exhibit A1 - 2.4 D-1.4 Progress Reports (Quarterly, Annually) ⚙️ Task Non-coding work item mgmt
Projects
Status: Done
Development

No branches or pull requests

2 participants