Complete all Get usecases

[abhishekbh]

https://github.com/thesentinelproject/threatwiki_node/wiki/API-Usecases---Gets

[jeromegv]

Retrieve Datapoints by SOC, says completed on the wiki, but couldn't see it in the code

[abhishekbh]

ah, you're right. As the commit message says, this is only supposed to be 'Get SOC by title', but I added in another unfinished commit by mistake. The Wiki is a mistake as well.

Fixing.

[jeromegv]

To which point do we want to "complete" that for the 1st release? I know we really just want to get all the API that we need for our UI, but what if we don't need all those possibilities yet? May be keeping it for another iteration? I can see the point of having more things in the API, to makes things easier to grow later on and get plugins to have access to more things, but considering the tight deadlines, wondering if we should focus on the core functionnalities to get it working for Sentinel people

[abhishekbh]

Well, so the only thing remaining are the date comparisons, which once done for one, will be copy/paste for all others. We can skip the user thing if you want, was that your concern?

Since we have 10 more days and only a few issues open, I think this is doable. Were you thinking otherwise?

[jeromegv]

What I'm realizing, and that's not on our list, is setting up some kind of workflow/user interface, for when people login and start adding datapoints.. a real-world usage of our app. Right now it's just dumping the data for each collection, which is fine because we will need it, but there's a bit more to it if we want people to use it. We might need to start some mockups before we get started on that, I can start drawing some things tomorrow.

[abhishekbh]

So did you mean UI design?

We can certainly tap into some in-house talent for that.

So the question here comes down what is the purpose of the first release. I've attached a file here (open index.html) which I presented at the last board meeting as the general timelines we were aiming for.

According to this, the purpose of this release was not to replace TW, but to be a general purpose CMS which we can provide to the community. The second milestone (2 months after) was supposed to be the TW replacement. That's why I was thinking of concentrating of functionality this time around.

Do you think that's a good idea? We could pull that second milestone up to 3 weeks from now if you wanted to make the TW replacement faster. That release cycle would be mostly UI and making the software actually usable for day to day functionality.

Let me know what you think.

Abhishek Bhatnagar

On Wed, May 30, 2012 at 11:50 PM, jeromegv < reply@reply.github.com

wrote:

What I'm realizing, and that's not on our list, is setting up some kind of workflow/user interface, for when people login and start adding datapoints.. a real-world usage of our app. Right now it's just dumping the data for each collection, which is fine because we will need it, but there's a bit more to it if we want people to use it. We might need to start some mockups before we get started on that, I can start drawing some things tomorrow.

---

Reply to this email directly or view it on GitHub:

https://github.com/thesentinelproject/threatwiki_node/issues/10#issuecomment-6027394

[abhishekbh]

Question about enabling search by user: The only way I know how to do this is the way we're search for socs by tags.

Which is:

• In user_actions, include the User Model!
• Then accept a username parameter in the api, and put that through the user model to get back a user object
• Match the _id of this user object against what is stored in the datapoint/soc/tag under createdBy

Is this the only way? Can populate be used to retrieve a user's id given their username only?