bavc / avaa Goto Github PK

https://bavc.github.io/avaa/artifacts/lengthwise_tape_expansion_or_shrinkage.html

https://bavc.github.io/avaa/artifacts/video_overwrite.html

Remove 0.85em; from the body CSS to bring the font size up to 1em.

Heya - there is a contributing.md and a contributors_guide.md. Are these duplicates? I tried to delete the contributing.md from my clone and push it or pull it but I'm still struggling a bit with how this works.

We have some documentation on how to add new information to existing artifacts and a ticket open to explain how to add new artifacts, but I think a style guide should be implemented regarding how artifacts are spoken of, etc.

https://bavc.github.io/avaa/artifacts/block_noise.html

If we add a favicon.ico at the top level, it will show up as the icon in browsers. We might have to add a link to the favicon somewhere in the Jekyll site. If someone wants to do this but needs help, just let me know!

https://bavc.github.io/avaa/artifacts/scratches_and_tape_wear.html

Right now, links are wrapped in a button to give style but that's no good, should be updated.

Do some testing on string manipulation and consolidate two search files (they are extremely similar)

I have an artifact I've seen in the wild a few times, and somewhat reliably from my own capture setup, where an MPEG-2 frame gets vertically smeared. I assume this is due to truncated data (the capture setup where I see it most often is an HDHomeRun Prime, which lets you record an MPEG-2 TS from cable by giving it a duration - I think sometimes the duration doesn't line up exactly with an MPEG-2 frame, resulting in this error. Unfortunately I don't keep all the original TS files so I don't have a raw TS to verify this).

Some examples:
https://twitter.com/neural_tv/status/807783247748939776
https://twitter.com/tv_sounds/status/836294900106809344

Film has problems too.

The relevant code is here, but I'm not sure what {% for category in categories %} is trying to access.

Need more documentation on how to add a new page to AVAA, for new artifacts.

https://bavc.github.io/avaa/artifacts/scratches_and_tape_wear.html

https://bavc.github.io/avaa/artifacts/ac_beat.html

As seen in the wikimedia sidebar (see screencap)

Especially important within the context of breaking links. Needs robust 404 page with explanation, ability to search, etc.

https://bavc.github.io/avaa/artifacts/incompatibility_between_television_standards.html

About page is very text heavy - maybe some images?

The screen captures of digital waveform monitors are hard to read. Maybe change the examples to QCTools waveforms? Assigned to @kellyhaydon.

https://bavc.github.io/avaa/artifacts/loss_of_color_lock.html

The hamburger pops up but it's maybe unclear how to get to the navigation

https://bavc.github.io/avaa/artifacts/dihedral_maladjustment.html

For looking prettier.

https://bavc.github.io/avaa/artifacts/low_rf.html

Need to investigate if there's a way to map and resolve links from MediaWiki pages to new page structure. This might be tricky because of the unfriendly URLs used in MediaWiki, but maybe some tricky-mapping can occur?

https://bavc.github.io/avaa/artifacts/crash_record.html

With rumors circulating over the past few days that Soundcloud is shutting down, it begets the question: What is the contingency plan for the demise of a platform AVAA uses to host example files? I don't think the Soundcloud issue is an immediate threat, but it can be used as an impetus to ensure we are prepared for an event similar to this.

Related, what is the plan for sample file ownership? BAVC, the primary host of this material, has had staff leave and new staff arrive, so what is the best way to document and relay information for a low-priority application like this one? Stanford acts as a secondary host, and what role do all of you play in this? In general, how do we avoid having things "lost in the shuffle"?

I was thinking recently, too, how if I had been a "good archivist" while doing the data migration from MediaWiki to this new site, I would have done a better job (and by 'better' I mean 'anything at all') at documenting what that process was like, for legacy purposes. Both for the migration and also for the collective decision-making we did in terms of reaching a consensus for what constituted a successful project migration, what was minimally determined as requirement for migration, and what became a "nice to have" instead of a requirement (and how that happened).

I would like the AVAA to have an open, written document for how to deal with these situations, as a preventative measure. This is kind of a good idea for any technology-based project, but this happens to be a small one that I care about and other people care about and is widely used as a resource. I think this document could go over what the dependencies are, where backups are located, who has access to them.. other things.

Some questions:
Where else do the sample files live?
Is there a collected, updated, active list?
Who has access to the Soundcloud/IA accounts?
Is there an alternative/better way to host and embed files?
Can we manage file access and file embedding within git, largely alleviating the first element of this issue completely?
Who "holds the keys" to relevant accounts, and how does that knowledge get transferred?

FWIW, I have no answers here. I suppose my role on this project could be summarized as technical-maintainer, but these are largely questions of institutionally-hosted maintainership. I did recently update the README to include all of the technical components I used to build this site, should that ever become relevant and need addressing and I'm not available to address it.

CC: @iamdamosuzuki @kellyhaydon @bturkus @hannahfrost @oceanofsound @michaelangeletti @ncoy

LOCKSS,

Ashley

It needs a CSS class added to make it look a little nicer.

It helps people know where they are! The homepage for AVAA just says "Home," which isn't very descriptive or helpful!

I'm trying to add an image, but what looks fine in GitHub: https://github.com/bavc/avaa/blob/master/_artifacts/dv_quilting.md

Is just placeholder square in prose. I've tried adding the image into Prose directly, but the same thing happens :(.

Important todo! Extend theme to make sidebar navigation appear in mobile!

https://bavc.github.io/avaa/artifacts/long_play.html

https://bavc.github.io/avaa/artifacts/venetian-blind_effect.html

When visiting the artifacts (tags) page, I often wish I had the option of viewing it in a mode similar to that of the AV Preservation Glossary: in alphabetical order by artifact with the navigational bar at the top. I also see the value of organizing by tags, especially since they can be clicked through from anywhere. Would it be possible to give users the option of browsing the artifacts either alphabetical by tags or by artifacts? I wouldn't want to task us with a lot of over-engineering, but I'm curious...

When searching for a keyword, each result comes up with the 'also known as' for that artefact. Many of them are null (no aka), in which case it would nice to hide that line.

I can do this, it should be a simple enough logic tweak to the search.js :)

https://bavc.github.io/avaa/artifacts/tape_deformation.html

Has an image, but would be better to have a video.

Assigning this too myself. Currently up to artifact G in my remote repo.

Hey @ablwr - I am trying to delete the kh/artifacts branch as it was created during my self-training phase and not a thing. I have not been successful. Is this something you can do easily?

On Firefox all these buttons do nothing when clicked.

I've started a dumping ground playlist for unknown audio artifacts: https://soundcloud.com/av_artifact_atlas/sets/unknown-audio-artifacts-1

Should we create a page or two off the home page for unknown audio and video artifacts to live? We could keep each one as an individual issue, but I imagine they won't get as many ears or eyeballs.

Site needs to be reviewed in the major browsers (Chrome, Firefox, Safari, Opera, IE) for functionality

There's now nothing at this link (https://www.bavc.org/preservation/resources/preservation-glossary), and this link (https://www.bavc.org/preserve-media/preservation-tools/preservation-glossary) is 'empty' - I don't see the Pres Glossary anywhere on the BAVC site. :(
I've changed the links in the AVAA to archived versions, but will the Glossary return at some point?

maybe just migrate what is on wikimedia for now

https://bavc.github.io/avaa/artifacts/sub-sampling_artifact.html

Based on conversation in this PR: #142

https://bavc.github.io/avaa/artifacts/luminance_noise.html

I noticed that currently, the video examples are just text links that are dead, e.g.:

http://avaa.bavc.org/artifactatlas/index.php/File:HEADCLOG2_2.mp4 on the video head clog page

Is there a plan to restore the videos? Let me know if I can help. :)

https://bavc.github.io/avaa/artifacts/mosquito_noise.html