...

Many_Fedora_users_use_the_'external_referenced_content'model_to_manage_the_link_between_their_data_and_the_Fedora_object.The_Fedora_APIs_provide_all_the_management_you_need_for'managed_content'but_there_is_a_key_component_missing_for'external_referenced_content'.__It_would_be_very_useful_if_the_management_API_supported_a_call_or_calls_that_optionally_managed_the_external_dataload_alongside_the_object_itself.Thus_when_a_new_object_was_ingested_from_a_FOXML_file,_the_call(s)_would_also_move_the_data_file_from_its_local_position_to_the_appropriate_datastore.If_a_datastram_was_then_updated,_a_new_version_of_the_datafile_would_be_uploaded_as_well_as_the_new_instance_of_the_datastream-thus_extending_the_crucial_idea_of_versioning_to_external_dataloads_too.This_would_presumably_involve_timestampng_the_data_file_in_some_way._At_the_moment,_we_shall_have_to_provide_this_functionality_outside_Fedora_and_I_think_it_is_something_that_should_be_in...

...

Simplified Object and Datastream Creation

Requested by: Matt Zumwalt

<blockquote>
Currently when creating a new object in Fedora, you have to create the skeleton FOXML for that object yourself and feed it into Fedora, despite the fact that the skeleton is basically the same for every new object you create. It would be really nice to have an alternate API method that creates an empty object for you based on a few optional parameters and returns the PID of that new object.
</blockquote>
<blockquote>
Also, there is the well known fact that Fedora requires you to use its upload servlet when creating new managed datastreams. I wish I could handle the uploads myself and give fedora a local (or network) file URL.
</blockquote>

...