The user constructs a query then sends it to a server, the server returns a list of items that match the query. For instance this may be a query:
INCLUDING artist contains "Pink Floyd"
and the results will look like this:
[ {"artist": "Pink Floyd", "title": "Another Brick In the Wall", "mimetype": "audio/mpeg", "album": "The Wall", "url": http://drive.google.com/blahblah.mp3" etc }, {"artist": "Pink Floyd", "title": "Money", "mimetype": "audio/flac", "album": "The Wall", "torrent_url": http://drive.google.com/blahblah.torrent" etc. }, {"artist": "Pink Floyd", "mimetype": "image/jpeg", "album": "The Wall", "url": http://drive.google.com/albumcover.jpg", "purpose": "album artwork" etc.} ]
You can add more to the query to filter out the content you don't want. The query language is much like a SQL WHERE clause. The query language is meant to be super simple and something your grandma could figure out.
The app then can retrieve the actual file from the url. The end user has no idea about the underlying file crap.
Please define how a "library item" is different from a "file".
Is it made of bytes that can be read into a buffer and accessed?
(If not, how can an H.264 video or MP3 object exist as a library item and be processed?)
Do you not have spaces which assign names to library items?
The Hyper-Text Transfer Protocol has already replaced the concept of "file" with "resource". A URI doesn't necessarily name a file.