Upload process

[Grizzly127]

I worked on the upload process:

I think the idea from semantic Kompakkt to keep the options on the right is good, so I used it here.
I divided the options on the right in mandatory and optional settings.
I corrected the fonts (using Open Sans everywhere)
I adjusted the buttons
I used the new stepper.
I reduced the options in "general information", before there were a lot more options in Kompakkt:

• Do we need any of these?

I had the idea to also use a stepper for the metadata settings, but as it also is a step in the upload process it won't work like that. I just want to keep the idea here:

@HeyItsBATMAN @ZetOE @lozanaross

[ZetOE]

Hey @HeyItsBATMAN, nice suggestion! I think most of the fields under general information were not used, so they can go right out. I would keep the set of metadata as small as possible as long as nothing important is missing. And the essential stuff for mappings is mandatory anyway.
I agree with the stepper suggestion - looks really good. Maybe @Grizzly127 has another idea of how to combine 2 steppers.

[ZetOE]

Ah sorry the suggestion is already made by @Grizzly127 , sorry thought it came from @HeyItsBATMAN . So all the props to you :) If it is true, which I assumed, that the fields are not used, they can go out. If this is not true, they have to stay, because it would also be a change of our data model...

[HeyItsBATMAN]

@ZetOE if we want to reduce/simplify the metadata form anyways, maybe we should have a meeting to decide what to keep & what to simplify.
That way we could, at the same time, document how our metadata looks and how it can be mapped to other formats. What do you think?

[ZetOE]

Yes, very good suggestion @HeyItsBATMAN . Maybe we can do the same with our annotation data model (but does not necessarily have to happen in the same meeting).

[ZetOE]

And: we should include CIDOC mapping.

[HeyItsBATMAN]

@Grizzly127 one thing I just noticed: Description should be a larger text area instead of a single line

[lozanaross]

@HeyItsBATMAN & @ZetOE I discussed some of the new design proposals with @Grizzly127 and we think this one, alongside #28 are a bit more complex and should be put on hold, until the higher priority ones - like fixing the nav / action bar, the login dialog, etc are completed. We should perhaps think about a labeling schema that can specify when something is higher priority than other issues. And maybe it's time we started using 'Projects' within the Git org page, to keep all issues across all repos a bit more organized at a glance.