You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enable the management of data as collections of files browsable and accessible bypassing DataJoint and organized in a way that makes sense to the user. DataJoint must maintain data integrity.
Operation
File tracking keeps the filenames and organization visible to and controllable by external users. The files are identified by their paths relative to the repository path. The datatype should be either file or file-suffix where the suffix can be up to eight character long.
Unlike external storage and attachments, file tracking does not rely on separate subfolders for each schema. Files must be accessible under the same locations by multiple schemas. Therefore, for tracked files, datajoint will create a local subfolder .datajoint where it will contain log files describing the tracking info. For example, for the file tracked at ephys/day1/file001.dat, datajoint will create the log file ephys/day1/.datajoint/file001.dat.log
The log file contains the information about the storing schema and the storing configuration.
The deletes do not delete the files and only update the corresponding log files. A separate cleanup utility will enable deleting the files that are not tracked by datajoint.
Purpose
Enable the management of data as collections of files browsable and accessible bypassing DataJoint and organized in a way that makes sense to the user. DataJoint must maintain data integrity.
Operation
File tracking keeps the filenames and organization visible to and controllable by external users. The files are identified by their paths relative to the repository path. The datatype should be either file or file-suffix where the suffix can be up to eight character long.
Unlike external storage and attachments, file tracking does not rely on separate subfolders for each schema. Files must be accessible under the same locations by multiple schemas. Therefore, for tracked files, datajoint will create a local subfolder .datajoint where it will contain log files describing the tracking info. For example, for the file tracked at
ephys/day1/file001.dat
, datajoint will create the log fileephys/day1/.datajoint/file001.dat.log
The log file contains the information about the storing schema and the storing configuration.
Insert
Inserting performs these tasks:
The file can be specified as the 2-tuple with the source and destination locations.
Fetch
Fetch performs the following operations:
The text was updated successfully, but these errors were encountered: