Some way is desired to attach new non-instantiation elements to existing PBCore records, possibly leading to some kind of command-line tool like:

addpbcoredata --to assetuuid --pbcoreTitle[titlevalue|titleType] 

automatically generation
identifierSource="WNYC Archive Catalog"
identifier=incrementing serial number during commit of each record.

to be defined.

Update the database model to store 'annotation' and 'annotationType' (whereas it current tracks only 'annotation'). I suppose this would be:
create_table "annotations", :force => true do |t|
t.integer "instantiation_id"
t.text "annotation", :limit => 16777215
t.text "annotationType", :limit => 16777215
end
Then parse existing annotation values into the two fields:
annotation value before first occurrence of a colon (if any) to annotationType
annotation value after first occurrence of a colon (or whole string if no colon) to annotation.

Add annotationType index to the MANAGE section as a vocabulary.

Edit UI to have the place annotationType as a combobox before each annotation.

For the XML rendering.
If there is an annotationType then use
${annotationType}:${annotation}
if not then
${annotation}

an annotationType is not required, an empty value should be allowable

from Marcos "Automatically migrate Asset ID to instantiation ID (we can easily add the decimal points or suffixes: .1, .2A, etc.). This will greatly improve our workflow, and minimize errors."

Allow config of auto-formatID based on identifier (of specified identifierSource) plus incremental suffix.

In the sample install, searching for 'merce' throws an exception. Other searches work fine.

The exception thrown is

ActiveRecord::RecordNotFound (Couldn't find all Assets with IDs (38590,42858,42836,40463,39208,40497,40475,39252,37396,38639,40469,40458,38641,42877,42834,40493,35576,40648,38633,38611) (found 19 results, but was looking for 20)):

generate xml expressions in 2.0 form from current data
see email and attachments from January 18, 2011 12:12:35 PM EST

for instance, support to:
add field labelled 'Series Title' that corresponds to a 'Series Title' picklist and is stored as

or similar support for annotations

On page load store top ~100 facets per faceted list. Display top ~14 but include a 'more...' option at the end of the list. The 'more' button would update the display to show the current displayed list +~10 additional values (until displaying ~100 or the whole list).

• and dateType controlled vocabulary
• (opt) highlight assetDate red if not conforming to ISO8601 regex (ISO 8601 is recommended but not required)
• (opt) calendar select drop down?

• allows inline xml in pbcoreExtension
• support import of PBCore 2.0 record with extensionEmbedded
• (opt) require data in extensionEmbedded is valid XML in data entry form on edit.

.

In 'View' options allow any valid http link to be clickable

for use in Firefox and IE. Currently they appear only a few pixels tall.

BUT we have to be careful here in the case where we're not actually deleting but rather merging.

I wonder how GitHub's issue tracker works?

Fix “modify or add instantiations” button within the asset edit page so that it saves the asset (right now it does not).

An oversight?

facet_display_name
query
default_number_of_values_to_display
sorting (alphabetically or by occurrence)

http://archive.danceheritage.org/?facet_Collection[]=Barnard+College+and+Columbia+University+Libraries

mwah ha ha ha!

allow for configurable guide search page. For example search boxes that just query the corresponding fields.
Collection
Series Title
Subject
Contributor

similar to how the auto-merge works for identifierSources but overwrite pre-existing instantiation. Thus if I upload an instantiation record, then change it, and re-upload it, if should overwrite the pre-existing record of matching formatIdentifier&formatIdentifierSource.

place at top of edit form, with combo box. Field may repeat.

For instance, "Add a new CD instantatiation" When used this would fill formatPhysical="Audio CD", formatSamplingRate="44.1 kHz", and other assumed metadata. After clicking "add a new CD instantiation' the user would still end up on the edit-instantiation page but some would be autofilled according to the settings.

because sunspot-rails is too damn clever for its own good, methinks.

Within the picklists section add a method to identify and easily distinguish what values are part of the official PBCore recommended vocabularies.

Not applicable to 'Identifier Sources', 'Subject', 'Genre', 'Format Identifier Sources', 'Extension Names', 'Essence Track Identifier Sources'.

Some fields aren't relevant to some applications of the system (such as audienceRating for non-broadcast material or formatFrameSize for non-video collections).
Provide a checklist in the MANAGE section to suppress deselected PBCore elements/fields.
Include these elements fields:
subject/authority
genre/authority
relationType/identifier
coverage/Type
audienceLevel
audienceRating
creator/Role
contributor/Role
publisher/Role
rightsSummary
extension/Authority

and all individual fields from instantiation and essenceTrack except
formatID/source
formatLocation
formatPhysical/formatDigital
formatGenerations
formatDuration

.

This is to help search db for records that are new or modified since the last search.

"Need to have two title elements as default, with titleType “episode” and “collection” as default."

Either by asset templates or config file

.

in many use cases instantiation and extension data isn't relevant to the user. we'd like to minimize this data in these cases. For instance, on login as guest show instantiation data as only a configurable summary, such as formatPhysical|Digital, formatGeneration, and formatLocation.

add configuration for the summarization that occurs in list view so that we could make titles or other data more prominent without edits to ruby display code.

Move the button for 'Destroy Found Set' down to where the 'Lend' and 'Merge' buttons are located in the administrative interface.

to allow possibility of tracking collaborative edits and/or merged records

Make multi-line similar to instantiation/Annotation or rightsSummary.

"We have created a dummy record for templates, but format (physical/digital) under Instantiation Information is not exported. Duration need not be exported under essenceTracks."

.

in the search bar, there's the 'Choose fields...' link that drops open a large list of fields for selection. Can we add a way to close this list? Then when the list ifs closed instead of 'Choose fields...', show the selected fields with a clear button, like 'Title, Subject [X]'. Clicking on 'Title, Subject' would open the list again, clicking of the X would unselect all field selections and revert the link back to 'Choose fields...'

Option 1: make series title list (and other list-based-on-other-lists) editable
or
Option 2: update the hard coded version as below:

I also have some additions to the list:

Adventures in Folk Music
Big Band Sounds
America & the World
American Composers Orchestra
American Story
Black Man in America
Brooklyn Academy of Music
Brooklyn Philharmonic Orchestra
Chamber Music New York
Chamber Music Society of Lincoln Center
Earplay
Evenings at the Thalia Book Club
Folksongs of America
Historic Heritage of Old New York
Inside Media
John Updike
Juggling Act
Life and Works
Margaret Juntwait
Music Maestro
National Association for American Composers
New York Queen of Commerce
Peace, Love, Creativity: Hope of Mankind
Roman Forum
Speaking for Ourselves
Steve Post
University of Chicago Roundtable
Vito Marcantonio Collection
WNYC Oral History Interviews
Youth in Government

And two corrections:

Citizens' Searchlight (not Citizen's Searchlight)
Housing Series (not Hudson Series)

it'd be nice to be able to search within specific fields, as we could with Sphinx.

Right now the user can see the essenceTrackIdentifier but not the source. Example: http://archive.danceheritage.org/assets/2b7e7729-8387-4846-ac41-57e026775af7

add annotationType vocabulary in manage section.
add annotationType dropdown in GUI besides every annotation type
for now suppress annotationType in PBCore XML (not valid PBCore 1.3) or append it to beginning of the annotation value with a colon delimiter.
in PBCore 2.0 this will probably be:
Sony

allow for both data entry via dropdown or free text data entry in selected fields

For WNYC, anybody connecting from 74.10.35.210 should be given the user role, but we should try to make it a little bit configurable of course.

wnyc prefers more restrictive dropdown boxes to the managed vocabulary terms, though others prefer comboboxes. Can we support both via the configuration file? Else can we simply switch the comboboxes for dropdowns in WNYC's instance.

For example, the site treats these URLs incorrectly and includes the closing parenthesis in the URL.

Contributors: Conductor: Heras-Casado, Pablo (http://lccn.loc.gov/no2010177786)
Contributors: Performing Group: International Contemporary Ensemble (http://lccn.loc.gov/n%202005053689)

we need to be able to specially create instantiations with video files in them, and to be able to play back those video files.

support for searching on beginning of strings

DHC needs a script which can be called like

$ ./upload-script filename.mp4 bd6f0df2-7ca2-49a4-9007-046f8ae09539

which will create a new video instantiation as appropriate.