Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
@internetarchive/search-service
Advanced tools
@@ -1,117 +0,0 @@
A service for searching and retrieving metadata from the Internet Archive.
yarn add @internetarchive/ia-search-service
In order to abstract the network connectivity layer and the environment-specific configuration from the result handling, the consumer should implement a search backend that implements the SearchBackendInterface
.
There are just two methods, one for fetching search results and the other for fetching metadata. They both return a Promise
that should contain JSON that matches a SearchResponse
object or a MetadataResponse
object.
// search-backend.ts
import { SearchBackendInterface, SearchResponse, MetadataResponse } from '@internetarchive/ia-search-service';
export class SearchBackend implements SearchBackendInterface {
constructor(baseUrl = 'archive.org') {
this.baseUrl = baseUrl;
}
async performSearch(params): Promise<SearchResponse> {
const urlSearchParam = params.asUrlSearchParams;
const queryAsString = urlSearchParam.toString();
const url = `https://${this.baseUrl}/advancedsearch.php?${queryAsString}`;
const response = await fetch(url);
const json = await response.json();
return new Promise(resolve => resolve(json));
}
async fetchMetadata(identifier): Promise<MetadataResponse> {
const url = `https://${this.baseUrl}/metadata/${identifier}`;
const response = await fetch(url);
const json = await response.json();
return new Promise(resolve => resolve(json));
}
}
Using the backend you created above, instantiate a SearchService
with it, craft some SearchParams
, and perform your search:
// search-consumer.ts
import { SearchService, SearchParams, SearchResponse } from '@internetarchive/ia-search-service';
import { SearchBackend } from './search-backend';
...
const searchBackend = new SearchBackend();
const searchService = new SearchService(searchBackend);
const params = new SearchParams('collection:books AND title:(little bunny foo foo)');
params.sort = 'downloads desc';
params.rows = 33;
params.start = 0;
params.fields = ['identifier', 'collection', 'creator', 'downloads'];
const searchResponse: SearchResponse = await searchService.performSearch(params);
searchResponse.response.numFound // => number
searchResponse.response.docs // => Metadata[] array
searchResponse.response.docs[0].identifier // => 'identifier-foo'
const metadataResponse: MetadataResponse = await searchService.fetchMetadata('some-identifier');
metadataResponse.metadata.identifier // => 'some-identifier'
metadataResponse.metadata.collection.value // => 'some-collection'
metadataResponse.metadata.collection.values // => ['some-collection', 'another-collection', 'more-collections']
Internet Archive Metadata is expansive and nearly all metadata fields can be returned as either an array, string, or number.
The Search Service handles all of the possible variations in data formats and converts them to native types. For instance on date fields, like date
, it takes the string returned and converts it into a native javascript Date
value. Similarly for duration-type fields, like length
, it takes the duration, which can be seconds 324.34
or hh:mm:ss.ms
and converts them to a number
in seconds.
There are parsers for several different field types, like Number
, String
, Date
, and Duration
and others can be added for other field types.
See src/models/metadata-fields/field-types.ts
metadata.collection.value // return just the first item of the `values` array, ie. 'my-collection'
metadata.collection.value // returns all values of the array, ie. ['my-collection', 'other-collection']
metadata.collection.rawValue // return the rawValue. This is useful for inspecting the raw response received.
metadata.date.value // return the date as a javascript `Date` object
metadata.length.value // return the length (duration) of the item as a number of seconds, can be in the format "hh:mm:ss" or decimal seconds
yarn install
yarn test
yarn lint
FAQs
A search service for the Internet Archive
The npm package @internetarchive/search-service receives a total of 225 weekly downloads. As such, @internetarchive/search-service popularity was classified as not popular.
We found that @internetarchive/search-service demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.