Persistent record keeping?

[kitsuta]

@UncleKage commented on Sat Sep 19 2015

A query from one of our directors:

"are there plans to implement persistent recordkeeping so we wouldn't have to do things like re-enter all the staff and dealer contact info each year?"

If so, is it on the plate for this year? If not, an it be? We are aiming to start up our pre-registration in about 2-3 weeks.

---

@kitsuta commented on Sat Sep 19 2015

It's on the docket, but not for this year. It's a rather massive undertaking and there's a lot of other stuff to get done before we can do that.

That being said, we can get around that for now by using the exporting and importing functions that already exist. MAGFest itself does manual importing of staffers each year, but we don't need to get that fancy - we can just use the CSV export/import.

---

@UncleKage commented on Sat Sep 19 2015

OK, no worries for this year, then. It's on the "let's do it someday" list.

On Sat, Sep 19, 2015 at 3:34 PM, Victoria Earl notifications@github.com
wrote:

It's on the docket, but not for this year. It's a rather massive
undertaking and there's a lot of other stuff to get done before we can do
that.

That being said, we can get around that for now by using the exporting and
importing functions that already exist. MAGFest itself does manual
importing of staffers each year, but we don't need to get that fancy - we
can just use the CSV export/import.

—
Reply to this email directly or view it on GitHub
Anthrocon-Reg/ubersystem#91 (comment)
.

---

@binary1230 commented on Mon Nov 16 2015

(Catching up on old emails)

this is one of my big priorities for Magfest, hopefully starting work after this upcoming event in Feb. I put a bunch of our initial brainstorming on the design decisions that need to be made over here: https://github.com/magfest/ubersystem/milestones/Persistent%20Ubersystem