Skip to content
This repository has been archived by the owner on Jan 20, 2024. It is now read-only.

Database Modification Discussion #142

Open
alxhrck opened this issue Feb 22, 2016 · 2 comments
Open

Database Modification Discussion #142

alxhrck opened this issue Feb 22, 2016 · 2 comments

Comments

@alxhrck
Copy link
Contributor

alxhrck commented Feb 22, 2016

I thought I'd start a thread regarding the needed modifications to the database schema. Hopefully we can consolidate the discussion to this issue.

@brianwarehime It would be helpful to create a new branch where we could commit code changes that effect the database without disrupting the master.

@alxhrck
Copy link
Contributor Author

alxhrck commented Feb 24, 2016

Table: Relationships
Columns: id, indicator_id, indicator_id

Table: Threat Actor
Columns: id, actor_name, actor_alias, comments, first_seen, last_seen, attribution, campaign_id

Table: Additional Attributes
Columns: id, attribute, attrib_value, indicator_id

Table: Indicators
Columns to add: campaign_id, source

Table: Campaigns
Columns: id, name, first_seen, last_name

@brianwarehime
Copy link
Collaborator

Agreed on the development branch 100%

That's something I'll be putting in place soon, we'll just have a development branch and master, and start using the git flow methodology. So, create a branch, merge to development, and if testing is good, we'll merge to master.

Regarding the database changes, I think that looks good. Definitely something we should all sit down and discuss more shortly. I apologize for my lack of updates lately, we are settling on our new house this week, and we've just been swamped with the moving process, so, hopefully in about two weeks I can get things back to normal and start development back up.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants