Hello
I have also removed some functions from bibdocfile (they were never used) Just in case anyone needs them, I provide a list: toplevel functions: generic_path2bidocfile normalize_version compose_file bibdocfile_url_to_fullpath get_docid_from_bibdocfile_fullpath decompose_bibdocfile_old_url get_format_from_url readfile BibRecDocs class: get_xml_8564 (used only in regression tests) cheers Piotr ________________________________________ From: Piotr Praczyk Sent: 28 June 2011 00:26 To: Samuele Kaplun Cc: Tibor Simko; project-cdsware-developers (CDS Invenio developers); Salvatore Mele Subject: RE: [inspire-dev] Limitations with having standalone BibDocs Hello Just a small part missing from previous discussion >> - BibDoc Python class in fact reflects needs of FullTexts. It should >> probably be stripped from functions that are typical to FT treatment. >> They should be moved to a subclass. (ie functions extracting fulltext) >Well it represent a document. Could you be more specific about which >functions are only related to fulltext? get_text get_text_path extract_text pdf_a_p has_text and in addition, some general flags are vert much BibDoc related ... and besides, maybe we should move methods responsable for displaying bibdocfiles to something like template ? Currently there are functions displaying HTML code inside the BibDoc (and similar) class. cheers Piotr
