html audio interface

first trial
(basically a copy and paste of Michael's code with tuna.js, soundboard.js)

customize your own search html

Utilize the 'Advanced Search' page on archive.org with javascript code to create a tailored search tool.

1) copy and paste the code block and paste to new textfile
2) link archive.org/advancedsearch.php to the new text file using form:
<form action="https://archive.org/advancedsearch.php" class="js-search-check_dates" name="searchForm" id="searchForm" method="POST" onsubmit="return validateForm()">

Who is Json and what is XML

Metadata

fields

here's metadata schema it seems like some fields are working but some not..

Title:

Subject:

Genre:

Description:

Collection:

Copyright Status:

Mediatype:

Contributor:

Coverage:

Runtime: (doesn't work)

custom metadata fields

Custom Metadata Fields Internet Archive strives to be metadata agnostic, enabling users to define the metadata format which best suits the needs of their material. In addition to the standard metadata fields listed above you may also define as many custom metadata fields as you require. These metadata fields can be defined ad hoc at item creation or metadata editing time and do not have to be defined in advance.

요약하면, Internet Archive는 특정 메타데이터 형식에 의존하지 않으며, 사용자가 필요한 대로 메타데이터를 자유롭게 정의할 수 있다: 기본 필드 외에도 사용자가 맞춤형 필드를 추가할 수 있으며, 필드의 이름이나 형식도 사용자가 직접 설정할 수 있다. 또한 자료를 업로드하거나 수정하는 과정에서 즉석에서 새로운 메타데이터 필드를 추가할 수 있음.

So..using Custom Metadata Fields is primarily useful when I know the custom metadata fields for the files I uploaded? because it would be difficult to know in advance or search for what custom fields others people used. Unless it's part of a collective project where everyone shares and agrees on the custom fields being used (like names and purposes).

Ways to check custom fields created by others:
* Reviewing the material directly: check the .xml file and see what's in there.
* Using the API: Internet Archive의 API는 사용자가 Internet Archive에 저장된 데이터에 접근하고 메타데이터, 파일, 검색 결과 등을 프로그래밍 방식으로 가져올 수 있게 해주는 인터페이스이며 이 API를 사용하면 웹사이트를 방문하지 않고도 Internet Archive의 방대한 아카이브에 있는 자료의 정보를 직접 가져올 수 있음.-->customized search html

Search trial

trial 1

If just search “elevator music” in the query:
With so many songs or albums has "elevator music" in them that seemingly have little relevance to the original purpose of the music(just a lot of cool artists being ironic), I try to narrow them down using the ‘community audio’ filter under ‘collection’ to avoid actual albums and songs.

results

meta.xml

Better, but still there are a lot of audio files that don't quite fit my search. From those unwanted files, I can look for metadata written in meta.mxl, figure out what I need to exclude using the boolean search.

improved results

Observation:
It took me an embarrassing amount of time to figure out that the collection filter search works with identifier names which can be found after the url:https://archive.org/details/ or in the metadata file written in xml.
(It was written right here but I just didn’t r e a d i t)

Question:
 What if I want results without searching for the title “elevator music”?
-> Can I search only using characteristics of the music, such as BPM or audio duration? Seems like I can’t, as there's no metadata type for that. Maybe a json or xml search can.........?🤷‍♀️I’m not even touching the bottom half of that advanced search page right now.

Other searches

Also found this gem--->

“Description: CORRUPT COURT CLERK”
“Subject: THE LADY THAT GOT ON THE PHONE AFTER I WAS PUT ON HOLD SOUNDS LIKE THE ONE FROM THE FIRST TAPE EARLIER TODAY”

The current state of my search HTML as of 071024

API

API stands for Application Programming Interface. It's like a key that allows you to access a service or program to retrieve or manipulate data. (간단하게 말해, API는 두 시스템이 서로 대화할 수 있게 해주는 약속된 규칙 또는 도구 모음이다. API는 프로그램이 요청을 보내고, 그 요청에 대한 응답을 받아오는 구조로 이루어져 있다.)

* Main Functions *
Data Transfer: Enables the exchange of data between two systems
Function Call: Allows you to use functions provided by other services or systems within your own program
Automation: Integrates various systems to interact automatically with each other(?)

Mixcloud API

API Documententation
Widget Javascript API Documentation

API example(radiowormrotterdam)

observation

MediaWiki API

exercise 1, Random_wiki_tinder.html

051024 prototyping with Manetta

MediaWiki Action API
Going through what MediaWiki Action API does, I found the API Random pretty interesting.

The goal is to build an html page that calls a random XPUBwiki page and displays it. Then add a swipe feature: swipe right(?) to save pages I'm interested in, or swipe the other way to skip if I'm not. Either way, swiping will load a new random page to explore.

exercise 051024 With Claudio, we managed to call the random pages on console. Now I wish to bring the page to be displayed on the screen. How?

User:Zuhui/Soundboard exercise

Contents