Sharing a book

[esanmiguelc]

Given I want to share a book
When I go to the application
Then I want to be able to fill out the identifying information about the book:

• Author
• Title
• ISBN

Edit 1:

Given I am on the homepage
And I want to share a book
When I click the "share a book" button
And I fill the identifying information about the book:

• Author
• Title
• ISBN

And I hit "share"
Then I should be sent to the Book detail page
And I should see the information I filled out

[YhorbyMatias]

So, is this the first step ?

[esanmiguelc]

Yep

[esanmiguelc]

@YhorbyMatias If you're going to grab the story, make sure you assign it to yourself, so that someone else doesn't start it as well.

[Willjobs94]

When we say "Share a book", does it means that the book does not exist in our DB, so we create it and "Share it" on our site ?

[esanmiguelc]

What we are trying to say here is that we want to make it available for other people to loan it. This story is probably not well defined as @wistcc pointed out. We need to determine what makes this story actually complete.

I don't necessarily care right now how we deliver this information to the user. Personally I'd call this done as soon as the user gets back a Book with the information filled out. This can be achieved by having the tests return a Book entity. We can figure out the delivery mechanism later.

Thoughts @amhed ?

[amhed]

Let's think about the user story:

As some who wishes to share a book I open the website and click on "Share Book". I get a screen where I can put in ISBN, Title, and Author, and at that moment I can share the book.

Let's not complicate ourselves, after completing this use case then we'll get to see others in which we realize we don't need to store the same book twice (and both the db scheme and the UX will adjust accordingly)

[wistcc]

I think we should create some initial issues to have something to start doing the other issues. I mean, to accomplish this issue (as I see) we should need to create the web project and at least the data access layer, but we haven't decided what kind of web project or what kind ORM we will use.

Also, I think we must add some well-defined acceptance cases to each issue in order to have a complete idea of what is required.

For example, what things do I need to do to accomplish this issue? @amhed @esanmiguelc

[esanmiguelc]

We can use MVC 6. I've updated the issue @wistcc

[amhed]

I wanted to do it very-TDD, to be able to share the books without having to create the web parts. But, fair enough, if it clarifies things then great.

Issues that we should create:

• Define Web Project with MVC6
• Define which ORM or Simple Driver to use for data persistence. What providers are currently available for no-sql db's on .net core?

@wistcc can you create this? currently on mobile

[wistcc]

Issues #12 and #13 created. Feel free to add or clarify anything there.