User Details
- User Since
- May 8 2019, 6:11 AM (94 w, 1 d)
Tue, Feb 23
Remove replace timezone from date
Change date from string to datetime
Mon, Feb 22
Remove Redundancy from Readme
Undo change in mapping_utils
Change SQL structure
Add readme in tests
Fri, Feb 19
Removed last_run_date table and add clearcode_env
Shift mapping code in mapping_utils
Add type annotations
Correct map_previously_data
Improve select statements
Use hstore instead of a single row table
Thu, Feb 18
Tue, Feb 16
Thanks for this
Reword commit message
Done, made the change
Reword commit message
Reword commit message
Mon, Feb 15
Add type of List[RawExtrensicMetadata] and change format of RawExtrensicMetadata
Sun, Feb 14
Change type of MetadataAuthority
Sat, Feb 13
Resolve Flake 8 error
Change input type of map_row_data_with_metadata
Fri, Feb 12
Change return type of mapping row with metadata
Change return type of mapping row with metadata
Change return type of mapping row with metadata
Thu, Feb 11
Change return type of map_row
Change return type of map_row
Change return type of map_row
Change return type of map_row
Wed, Feb 10
Mon, Feb 8
Sun, Feb 7
Tue, Feb 2
Map a row from clearcode toolkit with software heritage archive
Add feature to map a row from clearcode toolkit database with content and revision table from software heritage archive
Add feature to map a row from clearcode toolkit database with content and revision table from software heritage archive
This is to build a mechanism to map a row [path(Primary Key), content(binary data), last_modified_date(timestamp with timezone), map_error(error message while mapping), uuid] from clearcode toolkit database, with software heritage archive using content table for sha1 and revision table for sha1_git and extract required information from that row. Then return list of data that has been mapped and mapping status(if able to map every hash of that row, will return True, else return False) so the row that is not being able to map for now can be stored in a state, and can be mapped in future.
Add various exception classes in error.py that can be raised while mapping a row. Check if that row is a definition or harvest and also check if that row does not has invalid path, raise exception if path is invalid. If row is a definiton then map the data using map_definition and if it is a harvest then map it using map_harvest. Use storage instead of sql queries while mapping with the data inside archive. Add tests to cover all the cases and add docstrings to explain how every function works.
Mon, Feb 1
Add mapping for definitions and harvests
Use swh storage instead of sql queries to map sha1 with SWHIDs
Add different type of exceptions in error.py
Add function map_row, and try to check if the ID of the row is valid ID or not, if it is not a valid ID, then raise different exceptions defined in error.py. And if the ID is valid then check if the ID is a definition or harvest.
If the given ID is a definition then map the hashes with the archive (sha1 with content and sha1git with revision) and if able to map the defintion then return True,[(SWHID, TargetType(revision/content), Origin)], otherwise return None.
If the given ID is a harvest, then check the tool of the harvest (licensee, scancode, clearlydefined) and map accordig to the tool (map_licensee, map_scancode, map_clearlydefined), then return mapping status of that harvest (True if every sha1 of that harvest is mapped and False if failed to do it) and a list of data([SWHID,TargetType,None]).
Add tests to cover all the cases
Add mapping for definitions and harvests
Use swh storage instead of sql queries to map sha1 with SWHIDs
Add different type of errors in error.py
Add function map_row, and try to check if the ID of the row is valid ID or not, if it is not a valid ID, then raise different exceptions defined in error.py. And if the ID is valid then check if the ID is a definition or harvest.
If the given ID is a definition then map the hashes with the archive (sha1 with content and sha1git with revision) and if able to map the defintion then return True,[(SWHID, TargetType(revision/content), Origin)], otherwise return None.
If the given ID is a harvest, then check the tool of the harvest (licensee, scancode, clearlydefined) and map accordig to the tool (map_licensee, map_scancode, map_clearlydefined), then return mapping status of that harvest (True if every sha1 of that harvest is mapped and False if failed to do it) and a list of data([SWHID,TargetType,None]).
Add tests to cover all the cases
Add mapping for definitions and harvests
Use swh storage instead of sql queries to map sha1 with SWHIDs
Add different type of error classes in error.py
Add function map_row, and try to check if the ID of the row is valid ID or not, if it is not a valid ID, then raise different exceptions defined in error.py. And if the ID is valid then check if the ID is a definition or harvest.
If the given ID is a definition then map the hashes with the archive (sha1 with content and sha1git with revision) and return a valid SWHID, TargetType(revision/content), Origin
If the given ID is a harvest, then check the tool of the harvest (licensee, scancode, clearlydefined) and map accordig to the tool (map_licensee, map_scancode, map_clearlydefined), then return mapping status of that harvest (True if every sha1 of that harvest is mapped and False if failed to do it) and a list of data([SWHID,TargetType,None]).
Add tests to cover all the cases"
Add mapping for definitions and harvests
Add functions map_row, map_definition, map_harvest to check whether swh archive is able to map clearlydefined object or not
Add error classes for all conditions where metadata can be wrong or for an invalid ID
Add docstring for error class
Add mapping for definitions and harvests
Add functions map_row, map_definition, map_harvest to check whether swh archive is able to map clearlydefined object or not
Add error classes for all conditions where metadata can be wrong or for an invalid ID
Add mapping for definitions and harvests
Add functions map_row, map_definition, map_harvest to check whether swh archive is able to map clearlydefined object or not
Fri, Jan 29
Add mapping for definitions and harvests
Add functions map_row, map_definition, map_harvest to check whether swh archive is able to map clearlydefined object or not
@vlorentz made the suggested changes, thanks for a detailed review :)
Add mapping for definitions and harvests
Add functions map_row, map_definition, map_harvest to check whether swh archive is able to map clearlydefined object or not
Add mapping for definitions and harvests
Add functions map_row, map_definition, map_harvest to check whether swh archive is able to map clearlydefined object or not
Add mapping for definitions and harvests
Add functions map_row, map_definition, map_harvest to check whether swh archive is able to map clearlydefined object or not
Thu, Jan 28
Add mapping for definitions and harvests
Add functions map_row, map_definition, map_harvest to check whether swh archive is able to map clearlydefined object or not
Add mapping for definitions and harvests
Add functions map_row, map_definition, map_harvest to check whether swh archive is able to map clearlydefined object or not
Add mapping for definitions and harvests
Add functions map_row, map_definition, map_harvest to check whether swh archive is able to map clearlydefined object or not
Add mapping of definitions and harvests
Add mapping of definitions and harvests
Add mapping of definitions and harvests
Add mapping of definitions and harvests
Add mapping of definitions and harvests
Add mapping of definitions and harvest
Add mapping of definitions and harvest
Wed, Jan 27
Add mapping of definitions and harvests
Jan 20 2021
Add mapping of sha1 with swh ID
Add mapping of sha1 with swh ID
Add mapping of sha1 with swh ID
Jan 19 2021
Add mapping of sha1 with swh ID
Add mapping of sha1 with swh ID
Jan 18 2021
Add mapping of sha1 with swh ID