Closed ablwr closed 4 years ago
Here is the proof-of-concept branch: https://github.com/ablwr/avaa/tree/formats-collection
Also maybe this goes without saying, but this is JUST a proof of concept! I know this should contain Audio formats too!
There also may be a better way of thinking about these video formats, and putting them into categories of likeness instead of completely separate ones. That could use some more thinking around, I haven't thought a lot about it. Being as specific as possible is probably best?
FWIW I did change many of them to categories of likeness, like DV for all DV types, putting all Film together instead of individually, etc. This seems like the best approach for newbies, and each can get more granular within the page.
@DaleLore has been gathering information on decks and collecting analog video formats.
I was thinking adding a Formats collection (aka the same data concept as the Artifacts) would be a great addition to the AVAA. It would also be a good proof-of-concept for how some of the AVKID working group work might work out, if added to the AVAA.
I just did a proof-of-concept, it'd look something like this:
(I haven't added anything to the sidebar or index page obviously)
But basically, there'd be a Formats category and users working with a specific Format can click on it, see a description, links, and other helpful info, and then -- the magic bit -- is it will loop through all Artifacts that have Format: NameOfFormat
In the above example, I added
formats: [VHS]
to Bearding just as a test.Lorena and I think this will go a long way in helping one of the big pain points of AVAA for new users, which is kinda needing to already know the name of an error in order to find out what to do about it. This way, folks can go to the format they are working with and see all the associated artifacts and help narrow it down even if they don't know what its called. Or just what to be aware of when working with a specific format.
Would love to hear what others think! I will clean this sample up a bit and make a branch / pull request so that the adventurous can play around with it for themselves.