Using status to keep track of the archive as opposed to a separate collection

[kungpaogao]

Honestly, it makes no sense to create a separate collection now that I think about it.

This should be addressed in a big refactor update that includes #12. This can be addressed later in the dev cycle? Or now to avoid a cascading amount of changes?

Pros of updating:

• cleaner code/logic for checking across all furniture
• potentially cleaner code for front end since you don't have to have 2 namespaces for archive/inventory - need to think about this though

Cons:

• time - rewriting stuff is not fun